Skip to content

[Security] Enable allow_force_pushes on master for sensitive data cleanup #5444

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
casionone merged 1 commit into from
Jun 17, 2026
+11 −11
Merged

[Security] Enable allow_force_pushes on master for sensitive data cleanup #5444

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 11 additions & 11 deletions .asf.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,17 +58,17 @@ github:
merge: true
squash: true
rebase: true
# Temporarily disable master branch protection to allow force-push
# for cleaning sensitive information (passwords, internal IPs, domains)
# from historical commits per security ticket.
# Will be restored in a follow-up PR after the cleanup is complete.
# protected_branches:
# master:
# required_status_checks:
# strict: true
# required_pull_request_reviews:
# dismiss_stale_reviews: true
# required_approving_review_count: 1
protected_branches:
master:
required_status_checks:
strict: true
required_pull_request_reviews:
dismiss_stale_reviews: true
required_approving_review_count: 1
# Temporarily allow force-push on master to rewrite historical commits
# for cleaning leaked corporate sensitive information per security ticket.
# This line will be removed in a follow-up PR once cleanup is complete.
allow_force_pushes: true
notifications:
commits: commits@linkis.apache.org
issues: dev@linkis.apache.org
Expand Down
Loading