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
{{ message }}
This repository has been archived by the owner on Apr 4, 2024. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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
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.
The text was updated successfully, but these errors were encountered: