exclude/include rules in config #329
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
|
Thanks for this. I agree that ripping off Travis-CI makes a lot of sense -- for familiarity's sake if nothing else. |
pv
force-pushed
the
conditional-config
branch
2 times, most recently
from
de62db3 to
37cbdb1
Compare
pv
force-pushed
the
conditional-config
branch
from
37cbdb1 to
251ac19
Compare
pv
changed the title
|
I really like this. Very cool. |
mdboom
added a commit
that referenced
this pull request
Oct 27, 2015
exclude/include rules in config
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.
Exclude/include rules in configuration.
The present approach is sort of a ripoff from how Travis-CI does it.
Addresses gh-322
environment_typeandsys_platformperhaps should be allowed in include, but act as filters, similarly as in exclude? This would allow easy specification of os/environment dependent rules.