Use Full SHA1 Hash in Links (BB-3722)

Kevin Cox avatarKevin Cox created an issue

Currently only the first 12 characters of a commit are used in the links on the website. The issue is that if you were to like to a specific version of a file you would have to look up the full hash in a local repo in order to ensure the longevity of the link.

I think that it would be better to use the full 40 characters in link names to keep them valid but use the shortened version on the actual displayed content for ease of viewing.

Comments (2)

  1. Dylan Etkin

    Hi Kevin,

    Thanks for reporting. We have had a healthy debate internally as to if we should do this or not.

    I will add it to the backlog to further the discussion.

    It is not likely to be of high priority but it will get on the radar.

    Cheers,

    Dylan

  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.