Skip branches using both appveyor.yml and project settings
Please allow skipping branches using both approaches. When you fork a project for contribution you usually are not interested in the upstream branches, only in your feature branches. So when you update upstream branches you get useless builds, because they are already tested upstream.
For example say you fork project their/foo into your/foo, create branch feature and keeps merging/rebasing against master. Currently when you push these branches you also get a useless build for master in your/foo which is already triggered in their/foo. You could ignore master branch in project settings but they will be ignored per presence of appveyor.yml.
Therefore it would be nice if we could configure branches to skip in project settings and have them added to the ignored list from appveyor.yml. Or even better, we we could have a new project setting like Ignore all upstream branches (also Upstream project if not possible to automatically detect this). This new setting could be added to appveyor.yml so clones get this enabled automatically and the yml overwriting of the project settings continues to work the same way.
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by Feodor Fitsner on 30 Mar, 2016 03:53 AM
Thanks for your thoughts! I've added your comments to the existing issue: https://github.com/appveyor/ci/issues/716
Ilya Finkelshteyn closed this discussion on 25 Aug, 2018 02:05 AM.