ppkarwasz opened a new pull request, #456: URL: https://github.com/apache/logging-parent/pull/456
This change migrates branch protection from the deprecated [Protected Branches](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches) feature to [Rulesets](https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-rulesets/about-rulesets), using the new `rulesets` key added in apache/infrastructure-asfyaml#89. ## Why Rulesets? - Rules are publicly visible at https://github.com/apache/logging-parent/rules - The same ruleset can be applied to multiple branches simultaneously - `app_slug` identifiers replace fragile numeric `app_id` values The `required_signatures` rule was also dropped, as the project decided commit signing is not useful. ## Testing strategy The `.asf.yaml` file for Rulesets is only processed from the default branch. This means any mistake on `main` cannot be corrected without direct push access, which itself would be blocked by the broken rule. To avoid that trap, this PR: 1. Applies the new ruleset only to `test/rulesets`, leaving `main` temporarily unprotected 2. This allows direct fixes to `main` if the ruleset turns out to be misconfigured Once the ruleset is verified to be correct on test/rulesets, a follow-up PR will apply it to `main` and restore full protection. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
