Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tweak how push restrictions are handled #141

Merged
merged 1 commit into from
Apr 22, 2024

Conversation

jku
Copy link
Member

@jku jku commented Apr 18, 2024

This is a draft while discussion is ongoing, see sigstore/community#429

To avoid unnecessary churn in sigstore/community only set RestrictPushes if the project has users in the pushRestrictions list.

To avoid unnecessary churn in sigstore/community,
only set RestrictPushes if the project has users in the
pushRestrictions list.

Signed-off-by: Jussi Kukkonen <jkukkonen@google.com>
@jku jku force-pushed the tweak-push-restrictions branch from d459432 to 7f107f2 Compare April 18, 2024 15:12
@jku
Copy link
Member Author

jku commented Apr 22, 2024

I'm marking this ready-for-review: if you think it's worth testing I guess we just have to merge to main to to see how it goes :(

The reason I'm a bit hesitant is that while this probably does the right thing with current sigstore/community contents it does smell a bit: restrictPushes probably shouldn't only apply if the list of push exceptions (which our pushrestrictions really seem to be) list is longer than 0...

@jku jku marked this pull request as ready for review April 22, 2024 17:16
@haydentherapper haydentherapper merged commit 28695c1 into sigstore:main Apr 22, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants