[RFE] Use the Mergify config from the pull request destination branch rather than the default branch
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 339
- Forks
- 93
- PR merge metrics
- No merged PRs in 30d
Description
I've observed that Mergify uses the .mergify.yml file from my project's default branch, rather than using the .mergify.yml from the pull request's target branch. It would be nice if it used the policy from the destination branch so that we can keep the rule list simpler. I can achieve what I want by setting different rules for different branches in the default branch's .mergify.yml, but this makes the config more complex there.
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 tracing how the project selects the .mergify.yml policy for a pull request and compare the default branch with the destination branch. Define the behavior and tests around destination-branch configuration, with done meaning the destination branch's policy is used without requiring branch-specific rules in the default branch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github, yaml
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100