[4.6] ci: Travis: configure/restrict branch builds#6033
[4.6] ci: Travis: configure/restrict branch builds#6033blueyed wants to merge 1 commit intopytest-dev:4.6-maintenancefrom
Conversation
blueyed
force-pushed
the
ci-branches-4.6
branch
from
eefad6c to
fdc56da
Compare
(cherry picked from commit 851fc02)
blueyed
force-pushed
the
ci-branches-4.6
branch
from
fdc56da to
f9563ca
Compare
| - master | ||
| - features | ||
| - 4.6-maintenance | ||
| - /^\d+(\.\d+)+$/ |
There was a problem hiding this comment.
I usually add another explicit pattern in case people need to actually play with CI (especially useful in forks)
There was a problem hiding this comment.
There was a problem hiding this comment.
So you mean to include a prefix "test-me-*"?
I cannot really see why that would be useful - forks then have to use branches "test-me-foo" to have Travis run for their branch pushes, right?
The idea is that push branches for a "foo" branch are not run with this config, right?
I think real forks should also override that config then.
Regarding your use case we should just exclude "/^.-patch-./" only then?
btw: it would make more sense to discuss this on the master PR - I've only created this already, because I've thought it would be easy/non-controversial.
2 participants
No description provided.