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 originally required "sign/" prefix anticipating slightly more PRs that modify the git repository (but are not actually signing events). That does not seem to happen much as there should be almost nothing else in the repository, and the few that happen we can filter.
So:
I think we can consider every branch a signing event if there are changes in either targets/ or metadata/ (and branch is not "main" or "publish")
False positives should be easy for maintainers to handle -- just close the issue or don't create branches like that on the main repository
The text was updated successfully, but these errors were encountered:
I originally required "sign/" prefix anticipating slightly more PRs that modify the git repository (but are not actually signing events). That does not seem to happen much as there should be almost nothing else in the repository, and the few that happen we can filter.
So:
targets/
ormetadata/
(and branch is not "main" or "publish")The text was updated successfully, but these errors were encountered: