[doc] Branch reference syntax is imperfect

[webknjaz]

The docs show-case examples with @some-branch in remote URLs followed by a file path with slashes. But what if a branch name itself has slashes in it?

It is common to have branches like features/issue-number/branch-description or release/v1.0. Is it possible to still reference them w/o resorting to using commit SHAs? Would urlescaping of these slashes work?

[andreoliwa]

Is it possible to still reference them w/o resorting to using commit SHAs? Would urlescaping of these slashes work?

To be honest, I don't think this will work.
I didn't cover such possibilities because I was thinking mostly of common branch names like master, develop and main.
That's what happens when you work alone without code review. 😅

I'll try this when I have time, and see what breaks (or hopefully works).