Filters should allow for tags with branches not one or the other. It seems a pretty common use case to want only a branch to build but not run a deploy workflow unless branch:v1.0 tag has been added/approved/merged etc.
+1 for AND
I need this
Agreed!! Any traction on this??
Very much needed
I disagree. Tags don't belong to any branch. They are points in history just like branches, but separate from them.
I'd vote for user to be able to configure if he wants and/or
User should be able to select explicitly AND or OR, not automatically assume OR
AND is far more useful
far more useful
AND is more useful!
You won't be notified about changes to this idea.