Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFE] Use the Mergify config from the pull request destination branch rather than the default branch #348

Open
bowlofeggs opened this issue Feb 14, 2019 · 1 comment

Comments

@bowlofeggs
Copy link
Contributor

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.

@0xc0170
Copy link

0xc0170 commented Jan 14, 2020

This would be nice to have.

As docs state: "In the the default repository branch configured on GitHub — usually master.". However as the first stage for enabling mergify to a repository, would be to test it on a branch and creating PR against this branch to test the configuration and defined pull request workflow.
There is a simulator but someone would rather test it on PRs to get the config prototype working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants