damccorm opened a new issue, #26721: URL: https://github.com/apache/beam/issues/26721
### What needs to happen? During the last release, we had an accident that briefly caused the whole beam repo to be deleted and we needed to lift the branch protection rules briefly in order to rewrite history and fix git blame. In order to do this, we had to file a ticket with infra, but this is something that we can self service by moving our branch protection rules to the .asf.yaml file. Context - https://the-asf.slack.com/archives/CBX4TSBQ8/p1680790332979049 ### Issue Priority Priority: 2 (default / most normal work should be filed as P2) ### Issue Components - [ ] Component: Python SDK - [ ] Component: Java SDK - [ ] Component: Go SDK - [ ] Component: Typescript SDK - [ ] Component: IO connector - [ ] Component: Beam examples - [ ] Component: Beam playground - [ ] Component: Beam katas - [ ] Component: Website - [ ] Component: Spark Runner - [ ] Component: Flink Runner - [ ] Component: Samza Runner - [ ] Component: Twister2 Runner - [ ] Component: Hazelcast Jet Runner - [ ] Component: Google Cloud Dataflow Runner -- 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]
