choo121600 opened a new pull request, #148:
URL: https://github.com/apache/airflow-steward/pull/148
## Summary
This PR adds **Sweep 4** to the stale-sweep phase for PRs labeled `ready for
maintainer review`.
A PR enters Sweep 4 when:
- It has the `ready for maintainer review` label
- The last maintainer comment is ≥ 7 days old
- There has been no subsequent author activity (commit, comment, or review
reply)
Author activity includes:
- New commits (including force-push / rebase)
- Issue-level comments by the author
- Review-thread replies by the author
## Behavior
Sweep 4 splits based on branch health:
- **4a — Healthy branch** (`mergeable != CONFLICTING` and CI not failing)
→ Remove `ready for maintainer review` label (`strip-ready-label`)
- **4b — Unhealthy branch** (conflicts or failing CI)
→ Propose closing due to staleness/bitrot using `stale-ready-label-close`
template
→ Requires per-PR `Y/n` confirmation (no auto-close)
## Notes
- Uses existing GraphQL fields (`mergeable`, `statusCheckRollup`)
- No new GraphQL schema changes
- Adds two timestamps:
- `last_author_activity_at`
- `last_maintainer_comment_at`
## Changes
- `stale-sweeps.md`: Add Sweep 4 logic
- `actions.md`: Add `strip-ready-label`
- `comment-templates.md`: Add `stale-ready-label-close`
- `SKILL.md`, `fetch-and-batch.md`: Wire Sweep 4
## Test plan
- [ ] `tools/skill-validator` passes
- [ ] Cross-ref anchors resolve in rendered Markdown (4a/4b
headings, template anchor)
- [ ] Dry-run against `<upstream>` and check at least one PR
lands in 4a (healthy) and one in 4b (rotted)
- [ ] Verify 4a uses `[A]ll` without per-PR confirm, 4b still
pauses on each candidate
- [ ] Confirm a PR with an inline review-thread reply by the
author does NOT enter Sweep 4 (review-thread inclusion
in `last_author_activity_at`)
Closes #70.
--
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]
