Fixes .asf.yaml and update protection rules#3
Merged
Merged
Conversation
The automatic PR #2 did create any protection rules, since the update failed: https://lists.apache.org/thread/pqf7s9t1y0ctqpyjj8x0j3wtzrx8x5gt This PR: - Removes the invalid `profile` key from the `publish` object that caused the update to fail. - Adds `asf-site` to the branches protected from deletion and history rewriting. It also removes the `rel/*` and `release/*` patterns that don't exist in this repo. - Adds a rule for `asf-staging`, but only protects it from deletion. - Disables tags: we don't use them in this repo.
FreeAndNil
approved these changes
May 17, 2026
| - root | ||
| restrict_force_push: false | ||
| # There is no convenience notation for `creation` and `update`, so we need to use the raw rule syntax. | ||
| # |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The automatic PR #2 did create any protection rules, since the update failed:
https://lists.apache.org/thread/pqf7s9t1y0ctqpyjj8x0j3wtzrx8x5gt
This PR:
profilekey from thepublishobject that caused the update to fail.asf-siteto the branches protected from deletion and history rewriting. It also removes therel/*andrelease/*patterns that don't exist in this repo.asf-staging, but only protects it from deletion.