Conversation
Travis still defaults to 3.6, which is EOL!
Contributor
Author
|
Contributor
AzurePipelines still have some small advantages over GHA, but I do not see any reason to select Travis. |
Contributor
Author
|
I want to get a release out today, so I'm gonna merge this so we get the sample config fixes in the next release. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
In #1295 I noticed that some of the minimal configs are outdated. This PR fixes that.
It is kinda amazing that nobody has reported these issues with Travis and Azure Pipelines to us. I does make me wonder how many people are picking up CI services other than GHA these days.