Prioritize tags over master?

[rcdailey]

I have a workflow that triggers on push:. If I push a new commit on master with a tag, I get two builds: One for master, and one for the tag (e.g. v1.0). In this case, I want to never cancel the push event for the tag. Is it possible to specify this in the do_not_skip array? If not, I think it'd be great to have a way to do this.

[paescuj]

Such a behavior is currently not covered by skip-duplicate-actions. If so, then I think concurrent_skipping would be the more fitting option than do_not_skip.
You could handle this case by using two separate workflows, one which is triggered by pushes to the master branch and one by pushes of tags.

If you're interested in having this covered by skip-duplicate-actions, please consider funding it.