You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it would be great if Gitea had something like tag name rules. This would be the exact opposite of tag protection - repository administrators will be able to set up, for example, a regular expression or glob, to match tags.
If tag name wouldn't match, it will be rejected.
Why not use tag protection?
Someone will say:
We have already tag protection. Assume you have regular expression like this:
^\Av\d+\.\d+\.\d+\z$
Just use negative lookahead, and slightly modify your regex...
^(?!\Av\d+\.\d+\.\d+\z).*$
...and everything will be fine - no need to create another feature!
Unfortunately this is not possible, because we can't use negative lookahead - Go regexp uses RE2 syntax, not PCRE.
Conclusion
we would be sure that the tag names are correct
it's not that hard to implement, because you have already done tag protection
GitHub doesn't have this 👀
Screenshots
The text was updated successfully, but these errors were encountered:
Feature Description
Idea
I think it would be great if Gitea had something like tag name rules. This would be the exact opposite of tag protection - repository administrators will be able to set up, for example, a regular expression or glob, to match tags.
If tag name wouldn't match, it will be rejected.
Why not use tag protection?
Someone will say:
We have already tag protection. Assume you have regular expression like this:
Just use negative lookahead, and slightly modify your regex...
...and everything will be fine - no need to create another feature!
Unfortunately this is not possible, because we can't use negative lookahead - Go regexp uses RE2 syntax, not PCRE.
Conclusion
Screenshots
The text was updated successfully, but these errors were encountered: