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
root-signing-staging has a setup where sigstore-bot can push to two branches main and publish.
Pushing to both worked May 23rd 10:19 GMT+3. Then on May 24th 15:26 GMT+3 pushing to main worked but pushing to publish failed with "protected branch hook declined".
So something clearly changed in the config. I can see that main and publish have slightly different configuration so this is likely an easy fix, I'm just a bit worried how the setup changed?
To be clear: the yaml hasn't changed in months: I'm referring to the actual setup in the GHproject ... but possibly the branch protection settings haven't been applied after that last change
jku
changed the title
root-signing-staging branhc protection changed
root-signing-staging branch protection changed
May 24, 2024
root-signing-staging has a setup where sigstore-bot can push to two branches
main
andpublish
.Pushing to both worked May 23rd 10:19 GMT+3. Then on May 24th 15:26 GMT+3 pushing to main worked but pushing to publish failed with "protected branch hook declined".
So something clearly changed in the config. I can see that main and publish have slightly different configuration so this is likely an easy fix, I'm just a bit worried how the setup changed?
CC @kommendorkapten @haydentherapper
The text was updated successfully, but these errors were encountered: