Repository navigation
backport check fails for Python 2.7 fix that's not a backport #124
Description
python/cpython#8449 is a fix for a bug that doesn't appear in Python 3. There's no corresponding PR for master. But, Bedevere's backport check sees a PR for a maintenance branch, and insists that there should be a (GH-XXX) note in the title.
I didn't find guidance for this specific case in the devguide, but I think the correct thing to do is to merge without the (GH-XXX) note, ignoring the status check.
Activity
encukou commentedon Jul 28, 2018
I just noticed this is already being discussed in python/core-workflow#211
terryjreedy commentedon Jul 28, 2018
I just added python/core-workflow#278, suggesting a 'skip backport' label for this situation.
Mariatta commentedon Jul 29, 2018
This status check is optional so you can still merge the PR.
I think for now I'll just drop the check for
(GH-NNNN), and only checking for[X.Y], so we don't need a new label.Only check for the maintenance branch `[X.Y]` prefix. (#125)