Skip to content
This repository was archived by the owner on Nov 20, 2019. It is now read-only.

PR triggers should be more flexible about their target branches #225

Open
mmitche opened this issue Mar 16, 2016 · 2 comments
Open

PR triggers should be more flexible about their target branches #225

mmitche opened this issue Mar 16, 2016 · 2 comments
Labels

Comments

@mmitche
Copy link
Member

mmitche commented Mar 16, 2016

PR triggers today can apply to a specific branch. We don't easily allow through the Utilities to apply to multiple branches. This should be fixed.

In addition, a change to the ghprb should be made that can allow for the trigger to NOT apply to specific branches.

The other tracked branches for a repo should also be passed into the generators, so that logic like:

'Apply this PR trigger to master and to any other branch that isn't tracked'

@dilijev
Copy link
Contributor

dilijev commented Mar 16, 2016

👍

@mmitche
Copy link
Member Author

mmitche commented Jun 21, 2016

This is fixed by recent contributions to the GHPRB, pending merges and upgrades on our end.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants