Skip to content

Conversation

@flakey5
Copy link
Member

@flakey5 flakey5 commented Feb 3, 2025

No description provided.

@flakey5 flakey5 requested a review from a team as a code owner February 3, 2025 21:56
if: >
github.repository == 'nodejs/release-cloudflare-worker' &&
github.actor != 'github-merge-queue[bot]'
github.event.forced
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't we alert any push that was done through a PR merge? But also with this :)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't really think each pr merge should be an alert, the idea was to alert for direct pushes to the main branch w/o a pr

@targos
Copy link
Member

targos commented Feb 5, 2025

Instead of alerting on force pushes, I would recommend to make force pushes (or any pushes other than PR merges) impossible with a branch ruleset.

@ovflowd
Copy link
Member

ovflowd commented Feb 11, 2025

That should also be the case -- @flakey5 you have admin permissions you should be able to make changes.

@ovflowd ovflowd merged commit 7d9d2cc into main Feb 11, 2025
5 checks passed
@ovflowd ovflowd deleted the flakey5/20250203/fix branch February 11, 2025 21:26
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.

4 participants