Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-9358

Permalink to the "head" revision of a resource in a git repo

    XMLWordPrintable

    Details

    • Feedback Policy:

      Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Description

      Currently bitbucket only provides permalink ULR's for resources in a git repository by embedding specific commit hashes in their URL's, e.g.:

      https://bitbucket.org/<user>/<repo>/src/<commitHash>/<resource>?at=<branch>

      This is great for always viewing the state of that resource at that specific commit, but it doesn't work if you always want to view it at its latest revision, i.e. the "head" revision for the given branch of the repository.

      It would be great if it were possible to obtain such URL for any resource in a repository, even directories, possibly by removing the commit hash entirely and making the resulting URL always point to the "head" revision of the resource, e.g.:

      https://bitbucket.org/<user>/<repo>/src/<resource>?at=<branch>

      or maybe even:

      https://bitbucket.org/<user>/<repo>/src/head/<resource>?at=<branch>

      By providing any of those URL's, or something equivalent / more appropriate, we could e.g. copy & paste that into a mail and send it to a friend / co-worker, and rest assured that they'll always be looking at the latest incarnation of the resource. By embedding commit hashes in the URL's this becomes impossible, and I'm yet to find a way to keep commit hashes from creeping into the URL's.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            2bc1ef2f7e81 jmpp
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: