Locking/auditing for tags
Right now, it's basically impossible to have any protection around tags: * Anyone with write access to a repo can push any tags. * There's no auditing/logging of tag changes. Any number of things could be done to improve this: * Add an option to protect individual tags (or better yet, any tags that match a given regex/have a certain prefix), like how how branches can be protected. * Include tagging events in the per-organization audit logs. * Allow tag pushes to be locked down more tightly, like only allowing admins to push tags.
Posted by alecbz on Oct 13, 2017, 3:25 PM
Tags
Related issues
- The issue is really the extreme difficulty of programming them, especially for anything sequential (rather than combinatorial).
- I probably could have beared with it if it was only limited to programming, but it showing up in creative fields has made me feel all sor...
- I hate that I'm in deep enough to know what you mean.
- The biggest problem with “AI” is that big corps are shoving it down our throats.
- in the middel of a coding session with 5.6 sol.
- [Hero Run] 535B-A23B on 18T tokens
Raise real-world problems, find people facing the same issue, and discuss solutions.4,500 issues0 comments
reliability (Other)
The issue is really the extreme difficulty of programming them, especially for anything sequential (rather than combinatorial).
I probably could have beared with it if it was only limited to programming, but it showing up in creative fields has made me feel all sor...
I hate that I'm in deep enough to know what you mean.
The biggest problem with “AI” is that big corps are shoving it down our throats.
in the middel of a coding session with 5.6 sol.
[Hero Run] 535B-A23B on 18T tokens
I hate that this is how AI is being used..
inexperienced protobuf user here -- why do non-googlers generally use protobuf?
Locking/auditing for tags
Right now, it's basically impossible to have any protection around tags: * Anyone with write access to a repo can push any tags. * There's no auditing/logging of tag changes. Any number of things could be done to improve this: * Add an option to protect individual tags (or better yet, any tags that match a given regex/have a certain prefix), like how how branches can be protected. * Include tagging events in the per-organization audit logs. * Allow tag pushes to be locked down more tightly, like only allowing admins to push tags.
Comments (0)
No comments yet. Start the discussion.