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
bors-ng integration #22
Comments
@badboy you have a competitor! ;) I have some invites for https://aelitabot.xyz/ which basically the same thing, but written in Rust and with a worse name IIUC. |
aelitabot.xyz is shutting down on 2017-03-06. The maintainer recommends either switching to bors-ng or self-hosting. |
I have an instance of bors-ng running at http://not-a-robot.herokuapp.com/. I could open it up to others |
So, not-a-robot is back up and updated and public. If you still want it can be added here. |
FYI I have several repos using https://bors-ng.github.io now, works like charm |
Yup, it's basically the same, use what suits you best |
@badboy that looks pretty cool, but unless I'm missing something it seems like overkill for our level of activity right now. |
@TedDriggs nah, it isn't overkill. Using bors on other crates and it is fine for this one |
Moving discussion from #20 here:
Documentation is at http://homu.hellorust.com/
Authorized is whoever I put into the list.
This is all pretty manual right now (someday I will be as dynamic as homu.io)
Now to the sad part: It seems I would actually need owner rights to modify the right hooks, and I don't think you can give this to others on a user repository (only on organization repository).
So for now the integration has to wait until I figure out a way for you to execute this (or inserting the right hooks manually)
The text was updated successfully, but these errors were encountered: