-
Suggestion
-
Resolution: Fixed
If you use a naming convention where branches and tags are grouped using the standard directory separator, slash or '/', they cannot be linked to by their name, but must be linked to using the hexadecimal checksum identifier.
On a slightly related note, it would be nice if those groupings where combined to a hierarchy in the web UI. I use BitBucket for hosting full-history mirrors of some LLVM repositories, and the numerous Apple version tags clutter the list.
Other than those minor issues, I must say that I find your services to be excellent and very reasonably priced. Thank you, and I hope you enjoy the holidays!
[BCLOUD-408] Branches and tags with slashes in their name (BB-527)
| Workflow | Original: JAC Suggestion Workflow [ 3526762 ] | New: JAC Suggestion Workflow 3 [ 3594134 ] |
| Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
@dlenski I've posted a new issue that I think captures your comment: BCLOUD-14422
@nvenegas, this still does not seem to work for /src URLs.
For example, I have found no way to link to a file at the tip of a specific branch whose name contains a slash :-1:
https://bitbucket.org/:user/:repo/src/:branch_name/subdir/filename.txt
| Status | Original: GATHERING INTEREST [ 11772 ] | New: RESOLVED [ 5 ] |
Most URLs should now accept branch names with a / in them.
However, URLs for specific commits, e.g.,
- /:user/:repo/commits/:commit and
- /:user/:repo/commits/:commit/raw
don't accept branch names with a / in them.
Also affects tarball downloads (#5865) and the API (#5328).
This also happens even if you escape the slash with %2F.
Issue BCLOUD-7097 was marked as a duplicate of this issue.
| Status | Original: RESOLVED [ 5 ] | New: GATHERING INTEREST [ 11772 ] |
Thanks, @paulirish, absolutely! (Didn't know about your git-open project before, but it looks excellent… I've been trying to develop some more limited in-house code for linking to specific branches, and ran into the same problem.)