Reopened backport PR failed task will block auto merging
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 339
- Forks
- 93
- PR merge metrics
- No merged PRs in 30d
Description
Expected Behavior
@Mergifyio backportcreates a new PR.- mergify doesn't automatically deletes it's backport branches
Actual Behavior
@Mergifyio backportseems set on reusing the already open PR and branch.- mergify automatically deletes it's backport branches (not sure this was caused our issue)
Steps to Reproduce the Problem
@Mergifyio backport- Close the Mergifyio created backport PR to restart our CI tasks
->mergify bot deleted the mergify/bp/... branch - The rule doesn't match anymore . This action has been cancelled.
Specifications
- Pull Request URL: https://github.com/mozilla-mobile/focus-android/pull/6637
- Mergify Config URL: https://github.com/mozilla-mobile/focus-android/blob/main/.mergify.yml
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
Start by inspecting the referenced .mergify.yml and pull request #6637, then reproduce the backport sequence described in the issue: create a backport, close its PR, and observe the branch and rule state. Done means the backport creates a new PR as expected, preserves its branch, and the rule can continue after the PR is closed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100