remove Travis-CI instructions #341
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
We got a PR to organize Travis CI related doc fairly recently - #310 |
|
interesting. I wonder how many other @bcarter97 s there are out there. |
|
@SethTisue not many I think, we are having a fair few issues with Travis. |
|
@eed3si9n up/down decision? I'm still hoping for a merge here. it's an annoyance to 95% (maybe 99%) of our users to have to skip over this stuff in the doc. documenting alternative CI systems is worthwhile, but shouldn't get in the way of normal usage. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It's a GitHub Actions world these days.
I left the FAQ entry about other CI systems in place, and it now covers Travis-CI briefly.
If someone thinks the Travis-CI instructions should remain in-repo, I would suggest that they volunteer to reinstate them in a separate file (UPDATE: or in the FAQ entry, if they're short enough? just not sprinkled throughout!) in a separate PR.
At one time, it made sense for the readme to contain instructions for both CI systems inline. With GitHub Actions now so dominant, I feel rather strongly that it's too annoying for the reader to have to skip over the Travis-CI material.