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.
Every time I create a new open source project I have to go to the Travis documentation to find out what that one property I am looking for was called. It's so easy to get confused with Travis'
script
vs.test
on Circle, Travis'env
as an array ofkey=value
strings vs an object hash as on AppVeyor etc etc. I think most developers can relate.A .travis.yml compiles to a JSON representation, so we can validate it with a JSON schema, and the YAML language server does exactly that, giving awesome autocomplete and schema validation for YAML files through JSON schemas.
This schema is not perfect (I didn't add all deploy providers), but I went through every other docs page to collect all the possible options I could find.