This is related to PR https://github.com/ARMmbed/mbed-cli/pull/565, but not dependent on it.
This is an enhancement that:
You're referring to tags, not branches, correct?
Actually, branches could be used as well (branch heads).
If the reference is listed under git ls-remote, then it can be directly fetched from the remote, either from the ref name or the SHA.
But I would think that release tags would/should be the main use case.
@cmonr We have a policy of not allowing branches in .lib and .bld files, as they _can move_. We have defined library references to be fixed, and updates require _explicit_ user requests. As such, I can't accept a PR that automatically swaps a SHA ref; slow clone, can't change meaning; to a branch ref; fast clone, can change meaning.
Most helpful comment
@cmonr We have a policy of not allowing branches in
.liband.bldfiles, as they _can move_. We have defined library references to be fixed, and updates require _explicit_ user requests. As such, I can't accept a PR that automatically swaps a SHA ref; slow clone, can't change meaning; to a branch ref; fast clone, can change meaning.