Skip to content
This repository has been archived by the owner on Apr 4, 2024. It is now read-only.

Default to whatever GitHub PR integrations are enabled, don't require a bors.toml file #101

Closed
frewsxcv opened this issue Feb 23, 2017 · 2 comments
Assignees

Comments

@frewsxcv
Copy link
Contributor

Speaking for myself, the only integrations I have (besides bors-ng) is Travis CI. The only status I care about is Travis. Could bors-ng just default to whatever statuses are enabled on a repository as a default and a bors.toml can be used to override that? This means that with most of my repositories, a bors.toml is not needed.

@notriddle notriddle added the I-ux label Feb 23, 2017
@notriddle notriddle self-assigned this Feb 24, 2017
notriddle added a commit to notriddle/bors-ng that referenced this issue Feb 24, 2017
@notriddle
Copy link
Member

Does #102 look like an acceptable way to do it? GitHub doesn't really give me a list of all integrations on a repo (doesn't help that Travis is currently a "Service," and "Services" are being deprecated). I can figure that you want to use Travis if you have a .travis.yml file, though.

notriddle added a commit to notriddle/bors-ng that referenced this issue Feb 25, 2017
@frewsxcv
Copy link
Contributor Author

Does #102 look like an acceptable way to do it?

👍 💯

notriddle added a commit to notriddle/bors-ng that referenced this issue Feb 26, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants