Tag/Branch filters should be AND, not OR

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. 

  • Guest
  • Mar 19 2018
  • Taking votes
  • Attach files
  • Bastian Ermann commented
    12 Aug 23:21

    +1

  • Oleh Ka commented
    05 Jun 09:23

    +1 for AND

  • Rich Bannon commented
    11 May 18:09

    +1

  • A A commented
    06 May 22:19

    +1

  • fran memo commented
    30 Mar 14:14

    I need this

  • Ahmed AbdelMagied commented
    12 Mar 16:59

    +1 for AND

  • Jared Rohe commented
    20 Feb 16:53

    Agreed!! Any traction on this??

  • idan e commented
    December 19, 2019 06:28

    Very much needed

  • Andrew Z commented
    November 15, 2019 14:14

    I disagree.  Tags don't belong to any branch.  They are points in history just like branches, but separate from them.

  • Dean Shanahan commented
    November 13, 2019 18:24

    Up vote!

  • Emmanuel Apau commented
    October 28, 2019 13:48

    Upvote!!

  • Emmanuel Apau commented
    October 28, 2019 13:48

    Upvote

  • Marc Bornträger commented
    October 03, 2019 08:07

    I'd vote for user to be able to configure if he wants and/or

  • Tony Zhang commented
    September 30, 2019 15:18

    User should be able to select explicitly AND or OR, not automatically assume OR

  • Matthieu Guigon commented
    September 06, 2019 10:13

    Upvote!

     
  • Stephen Lester commented
    September 04, 2019 16:53

    Upvote!

  • Brian Gupta commented
    August 30, 2019 16:57

    AND is far more useful

  • David Morais commented
    July 17, 2019 22:43

    Up v00ting

  • Temitope S commented
    June 25, 2019 15:40

    far  more useful

  • Nguyen Chien commented
    March 01, 2019 01:41

    AND is more useful!