Use revision number to get changesets in REST API (BB-894)

adamschmideg avataradamschmideg created an issue

When retrieving changesets, the REST api currently seems to support only changeset ids. If I don't know the hash for a repository with a longer history, I can't get the first commit. My feature request is to keep the current scheme /repositories/USERNAME/REPO_SLUG/changesets/NODE/, but NODE could mean either a hash, or a revision number.

Comments (2)

  1. David Chambers

    Revision numbers really shouldn't be used in this way. Changeset hashes are consistent across forks; revision numbers are not necessarily.

    You should be able to retrieve the first commit by hitting the /changesets endpoint once or twice, then — having ascertained the commit's hash — hitting the /changeset endpoint.

  2. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.