Skip to content

docs: format Mergify policy plan #546

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
KooshaPari merged 1 commit into from
Aug 29, 2026
Merged

docs: format Mergify policy plan #546

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
21 changes: 11 additions & 10 deletions docs/superpowers/plans/2026-08-29-mergify-no-human-review.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,7 @@
### Task 1: Remove Mergify human-completion predicates while retaining CI gates

**Files:**

- Modify: `.mergify.yml:4-26,67-79`
- Test: inline Ruby policy assertions against `.mergify.yml`

Expand Down Expand Up @@ -45,26 +46,26 @@ Expected: fail because the current merge rule still contains
Replace the merge rule heading and name with:

```yaml
# Auto-merge when all configured CI checks pass.
- name: Auto-merge when CI green
# Auto-merge when all configured CI checks pass.
- name: Auto-merge when CI green
```

Delete these human-completion condition entries, and no other safeguards:

```yaml
- "#approved-reviews-by>=1"
- "#review-requested=0"
- "#approved-reviews-by>=1"
- "#review-requested=0"
```

Keep these merge conditions exactly:

```yaml
- check-success=ci
- check-success=lint
- check-success=typecheck
- check-success=test
- -conflict
- -closed
- check-success=ci
- check-success=lint
- check-success=typecheck
- check-success=test
- -conflict
- -closed
```

- [ ] **Step 3: Run policy validation**
Expand Down
Loading