Skip to content

[INFRA] Restore master branch protection after history cleanup#5453

Open
aiceflower wants to merge 1 commit into
apache:masterfrom
aiceflower:restore-master-protection
Open

[INFRA] Restore master branch protection after history cleanup#5453
aiceflower wants to merge 1 commit into
apache:masterfrom
aiceflower:restore-master-protection

Conversation

@aiceflower

Copy link
Copy Markdown
Member

Summary

  • Removes the temporary allow_force_pushes: true flag added in [Security] Enable allow_force_pushes on master for sensitive data cleanup #5444 to enable rewriting historical commits containing leaked internal credentials.
  • The cleanup across all branches (master + 13 release branches + fix-master-compile) and 40 tags is complete; this PR restores master branch protection to its standard configuration.

Context

Follow-up to the ASF Infra ticket for rewriting leaked corporate credentials in git history. With the history rewrite complete and verified (0 sensitive hits across all 62 refs), the temporary force-push allowance is no longer needed.

Test plan

  • Verify .asf.yaml syntax valid (yaml parser)
  • After merge, confirm GitHub reports master as protected with allow_force_pushes: false
  • Confirm required_status_checks and required_pull_request_reviews still active

🤖 Generated with Claude Code

Removes the temporary `allow_force_pushes: true` flag that was added
in PR apache#5444 to enable rewriting historical commits containing leaked
internal credentials. The cleanup across all branches and tags is
complete; master branch protection is restored to its standard
configuration.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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.

1 participant