You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The main reason for this is that GitHub has a built-in merge queue now that is publicly available... More importantly, there’s a bunch of bugs in bors-ng that we can’t fix, but they can.
Github merge queues seem overall better than bors-ng due to its integration with the service itself, and unfortunately the public instance already throws warnings and will eventually go down. This is acceptable for the projects that self-host a bors instance and cannot change their workflow, but I think in this project we can try new features.
In the bors-ng forum it was said, that bors will most likely continue to work, until GH's merges queues are stabilizes. This issue should definitely be addressed before then, but for now I'm focussing on other issues.
The main holdup on merging #132 is that the bors try comment would be lost. That one is super useful, since the normal CI only runs on linux, while the bors tests run on windows, linux, and macos.
On May 1, 2023 bors-ng became deprecated.
Github merge queues seem overall better than bors-ng due to its integration with the service itself, and unfortunately the public instance already throws warnings and will eventually go down. This is acceptable for the projects that self-host a bors instance and cannot change their workflow, but I think in this project we can try new features.
More on merge queues here and here.
The text was updated successfully, but these errors were encountered: