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

handle bors-ng shutdown #313

Open
duckinator opened this issue May 11, 2023 · 3 comments
Open

handle bors-ng shutdown #313

duckinator opened this issue May 11, 2023 · 3 comments

Comments

@duckinator
Copy link
Owner

duckinator commented May 11, 2023

bors-ng has been deprecated. we should either self-host an instance, or move to an alternative (e.g. GitHub's Merge Queues).

EDIT: It seems that, as of November 7 2023, the public bors-ng instance has been down for multiple days.

@duckinator
Copy link
Owner Author

apparently Merge Queues aren't available for users, only organizations.

for some reason.

@nbraud
Copy link
Collaborator

nbraud commented Oct 30, 2023

Yeap, it is the worst. :/

@duckinator
Copy link
Owner Author

It's also very bizarre given that they published a post on the GitHub blog back in July that was titled "GitHub merge queue is generally available"... only to go on to mention that it's specific to "teams".

(As best I can tell, when they say team they mean organization? I'm not sure why they use the wrong term for their own product...)

@duckinator duckinator changed the title handle bors-ng deprecation handle bors-ng shutdown Nov 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants