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

allow customizing the command trigger #461

Merged
merged 1 commit into from Sep 17, 2018

Conversation

Projects
None yet
2 participants
@indirect
Contributor

indirect commented Sep 16, 2018

This allows self-hosted copies of bors to choose their own command trigger. For example, this will allow us to silently replace our aging Homu mergebot with a bors-ng mergebot, without having to retrain all our contributors to use a different name.

allow customizing the command trigger
This allows self-hosted copies of bors to choose their own command
trigger. For example, this will allow us to silently replace our aging
Homu mergebot with a bors-ng mergebot, without having to retrain all our
contributors to use a different name.
@notriddle

This comment has been minimized.

Show comment
Hide comment
@notriddle

notriddle Sep 16, 2018

Member

Could you add a note about it to the README?

Member

notriddle commented Sep 16, 2018

Could you add a note about it to the README?

@notriddle

This comment has been minimized.

Show comment
Hide comment
@notriddle

notriddle Sep 17, 2018

Member

bors r+

Member

notriddle commented Sep 17, 2018

bors r+

bors bot added a commit that referenced this pull request Sep 17, 2018

Merge #461 #462
461: allow customizing the command trigger r=notriddle a=indirect

This allows self-hosted copies of bors to choose their own command trigger. For example, this will allow us to silently replace our aging Homu mergebot with a bors-ng mergebot, without having to retrain all our contributors to use a different name.

462: Isolate syncs between installations r=notriddle a=notriddle

This particular case was brought on by a repository that was added to bors-ng and blocked by GitHub for ToS violation. Since this doesn't automatically remove the repo from the installation, bors would find the repository there, then fail to synchronize it.

Co-authored-by: Andre Arko <andre@arko.net>
Co-authored-by: Michael Howell <michael@notriddle.com>
@bors

This comment has been minimized.

Show comment
Hide comment
@bors
Contributor

bors bot commented Sep 17, 2018

@bors bors bot merged commit 09dbe89 into bors-ng:master Sep 17, 2018

3 checks passed

Taskcluster (pull_request) TaskGroup: success
Details
bors Build succeeded
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details

notriddle added a commit to bors-ng/bors-ng.github.io that referenced this pull request Sep 17, 2018

Add bors-ng/bors-ng#461
Add @indirect as a new contributor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment