Multiple tags not supporting
See original GitHub issueHello,
I’m trying to give multiple tags with single merge to dev but I’m only getting the first tag support
feat(testing-branch): ‘Testing branch’
fix(fixing-branch): ‘Fixing branch’
chore(Aligning): ‘Chore testing’
Result:
Features
- testing-branch: ‘Testing branch’ (#commentNo)
Issue Analytics
- State:
- Created 4 years ago
- Comments:8
Top Results From Across the Web
running multiple Cucumber tags are not working · Issue #207
Issue description multiple tags are not running using cucumber tag option. working for the single tag only Steps to reproduce $ yarn run ......
Read more >Solved: Tags we are passing multiple tags like @Smoke and
Solved: We are passing multiple Tags in CucumberOptions class which is not running and getting error message as 0 scenarios-
Read more >(Cucumber) Multiple tags are not working properly
To get the proper result, have to run the feature file using the following tag expression: "(@tag1 or @tag2) and (not @tag3)".
Read more >Passing multiple tags through @CucumberOptions is ...
I am using Cucumber version 5.7.0. How can i run multiple tags now? import org.junit.runner.RunWith; import io.cucumber.junit.Cucumber ...
Read more >Add Multiple Tags from a Collector Using Historian Administrator
Select the Add Tags From Collector link in the Tag Maintenance page. · Select a collector from the Collector drop-down list. · In...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Each of your commits should contain a
feat:
,fix:
… prefixed comment as long as the feat, fix etc. are completed. Otherwise you’d use a neutral comment. Although your PR may list those prefixed comments in the description as well (although not required), no changelog tool will parse/use more than the first line (and the CHANGE BREAK) to generate different list items.2 alternative Best Practices here, depending on your use case/team convention:
1 feature per 1 PR
you could also do:
multiple features per 1 PR
The important things:
Oh wow thanks 😃