Can standards tags be applied to commits only for the standard they tag?
Given the current merge process (CRs are all agreed and merged back in to a single meeting branch), is there a sane way to add the standards tags such that they actually label a commit which represents the changes to that standard (as opposed to the output of the meeting)?
The preload script that populated the repo is able to do this because it doesn't use the branching strategy; each new version is a single commit which can then be tagged.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information