-
-
Notifications
You must be signed in to change notification settings - Fork 160
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
Migrate from bors to GitHub merge queues #337
Conversation
API docs are being generated and will be shortly available at: https://godot-rust.github.io/docs/gdext/pr-337 |
747aa8a
to
03a5a6d
Compare
Out of interest |
03a5a6d
to
4928792
Compare
Needed update of the bors config file. |
tryBuild failed: |
4928792
to
164c48b
Compare
bors try |
tryBuild succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page. |
Closes #255.
Extends the
minimal-ci
with a few more jobs that always run. One option would be to make this conditional on draft/ready PR, but that isn't done for now. We can adjust the number of jobs depending on what we find useful.full-ci
remains as is and will run whenever a PR reaches the front of the merge queue. It rebases the commits onmaster
and thus always runs checks against the latest version.For now, bors is still active, but I don't know if it can still be used with new branch protection rules. Over time,
bors try
will no longer be possible and has no equivalent in the merge queue. This should be OK by having a few more checks in the minimal CI; we could also add all checks there, with two stages (and 2nd only running after 1st passes).