Workflows should not require approval by default (support autonomous progress)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 8m
- Merged PRs (30d)
- 3
Description
Captured from Idea discussion during cleanup
Original discussion: https://github.com/akasper/plate/discussions/125 (2026-05-29, @akasper)
CI workflows should be heavily-gated and staged in order to ensure that we're never wasting cycles. However, requiring a human in the loop to approve workflows gets in the way of autonomous progress. We should provide guidance and default configuration that PRs should approve workflow runs by default.
This is a stub issue created from the Ideas category. Flesh out with specifics on which workflows, required status checks, and config in .github/ or .plate.
See related autonomy work (e.g. Epic #470).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Idea discussion, Epic #470, and the existing workflow configuration in .github/ or .plate. Identify which workflows, required status checks, and approval settings are in scope; done means the issue documents specific defaults and provides configuration that supports autonomous PR progress without wasting CI cycles.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100