Add condition attribute for unresolved PR comments
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 339
- Forks
- 93
- PR merge metrics
- No merged PRs in 30d
Description
My org has a style of leaving final 'nit' comments and approving assuming they'll be fixed before merge but it seems there's no way to tell mergify to not merge if there are open comments.
The alternative would be to create a status check for open comments but it seems round about. :)
Thanks!
Contributor guide
No contributing guide indexed for this repository
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
No files or tests are named. Start by checking how Mergify conditions expose GitHub pull-request review state and whether unresolved comments are available from the relevant API; done means a condition can prevent merging while review comments remain unresolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100