Repository navigation
Commit e412ab5
authored
chore(.asf.yaml): null out main branch protection to clear stale rules (#11)
## Summary
- Sets `github.protected_branches.main: ~` in `.asf.yaml`.
## Rationale
The previous PR (#7) removed the `protected_branches` block entirely,
but ASF INFRA only applies settings that are present in `.asf.yaml` — it
does not clear settings when keys are simply omitted. The required
status checks (`Java (spotless)`, `Rust (cargo fmt)`) therefore remain
configured on `main` and continue to block every PR, because the
workflow that would produce those check contexts is also gone.
Explicitly setting `protected_branches.main` to YAML null (`~`) tells
INFRA to clear the existing branch protection rules on `main`. Branch
protection can be reintroduced later once CI is in place.1 parent 80eaf81 commit e412ab5
1 file changed
Lines changed: 2 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
47 | 47 | | |
48 | 48 | | |
49 | 49 | | |
| 50 | + | |
| 51 | + | |
50 | 52 | | |
51 | 53 | | |
52 | 54 | | |
| |||
0 commit comments