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

Explore using Bors or mergify #746

Closed
patjouk opened this issue Mar 11, 2020 · 2 comments · Fixed by MozillaFoundation/foundation.mozilla.org#4372
Closed

Explore using Bors or mergify #746

patjouk opened this issue Mar 11, 2020 · 2 comments · Fixed by MozillaFoundation/foundation.mozilla.org#4372
Assignees
Labels
Milestone

Comments

@patjouk
Copy link
Contributor

patjouk commented Mar 11, 2020

Maybe we can try bors to find a way to schedule merge of PRs?

From the doc:
Once you’ve set it up, instead of clicking the green “Merge Button”, leave a comment like this on the pull request:

bors r+

Equivalently, you can comment the following:

bors merge

The pull request, as well as any other pull requests that are reviewed around the same time, will be merged into a branch called “staging”. Your CI tool will test it in there, and report the result back where Bors-NG can see it. If that result is “OK”, master gets fast-forwarded to reach it.

@patjouk patjouk added the devops label Mar 11, 2020
@patjouk patjouk self-assigned this Mar 11, 2020
@cadecairos cadecairos added this to the Mar 23 milestone Mar 11, 2020
@patjouk
Copy link
Contributor Author

patjouk commented Mar 12, 2020

https://mergify.io/ looks even more perfect! (free for open source)

@patjouk patjouk changed the title Explore using Bors Explore using Bors or mergify Mar 12, 2020
@patjouk
Copy link
Contributor Author

patjouk commented Mar 13, 2020

Mergify looks exactly like what we need, and it's already approved by MoCo security. I opened a bugzilla ticket since I don't have enough permissions to add the repo myself https://bugzilla.mozilla.org/show_bug.cgi?id=1622262

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

Successfully merging a pull request may close this issue.

2 participants