Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-5513

Improve branch-utils REST API documentation to clarify what information is returned about branches

XMLWordPrintable

    • 4
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      The /rest/branch-utils/1.0/projects/{projectKey}/repos/{repositorySlug}/branches/info/{changesetId} REST endpoint documentation states the following:

      Gets the branch information associated with a single changeset from a given repository.

      The documentation should be updated to include clarification that once a commit is on master (or whatever the default branch is) Stash considers it "merged" and will only show this commit as existing on master. Without this clarification, it's easy to think that all branches that this commit exists on should be returned regardless if it exists on master.

              tzutis@atlassian.com Tom Zutis (Inactive)
              jethomas Jeff Thomas
              Votes:
              3 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: