Bedevere is a little trigger-happy closing PRs
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 141
- Forks
- 62
- Avg merge
- 5m
- Merged PRs (30d)
- 2
Description
For example, it closed https://github.com/python/cpython/pull/155197 today, because "PRs attempting to merge a maintenance branch into the main branch are deemed to be spam and automatically closed." However, this PR was not attempting to do that, it had a branch named 3.16 with a commit with a fix. I'm not familiar with the logic here behind this, but I think a little sanity check would be good to avoid spurious closures in the future.
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 by tracing Bedevere's logic for identifying maintenance-branch-to-main pull requests, using pull request 155197 as the reproduction case. Check how branch names and commits are classified, then verify that a valid fix branch is not closed while genuine maintenance-branch merges still are.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- ci-cd, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100