Open davidjb opened 7 years ago
There shouldn't be a restriction with Git File Bridges to branches; just provide a text box area where a user can type a gitrevisions string (such as HEAD~1, branch name, tag name, a SHA hash, etc) -- grants access to anything that Git without any extra API calls to Git.
Reported at https://squizmap.squiz.net/9092
The JCU Web Framework uses git tags in order to manage release versions. Without the ability to 'checkout' a tag in a Git file bridge, we have to workaround our release schedule and branches are more ephemeral than tags.
A semi-workaround is to create branches in the git repository and use them like tags.