question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Multiple tags not supporting

See original GitHub issue

Hello,

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:closed
  • Created 4 years ago
  • Comments:8

github_iconTop GitHub Comments

1reaction
khatastroffikcommented, May 6, 2020

… my PR after commits. …

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

commit 1: "some work done on feat A" (note: no prefix here)
commit 2: "some more work done  on feat A" (note: no prefix here)
commit 3: "some final work  on feat A" <-- the feature A is completed here, but it's a neutral commment = no prefix here!
PR: "feat(A): allow the user to..." <-- PREFIX (optional: add all the comment above)

you could also do:

...
commit 3: "feat(A): allow the user to..." <-- PREFIX the feature A is completed here (optional: add all the comment above)
PR: "Please review the features A" <-- neutral comment (no need for more description here, no prefix here)

multiple features per 1 PR

commit 1: "feat(X): add function X" <-- PREFIX the feature X is completed here !
commit 2: "feat(Y): add function Y" <-- PREFIX the feature Y is completed here !
commit 1: "feat(Z): add function Z" <-- PREFIX the feature Z is completed here !
PR: "Please review the features X, Y and Z" <-- neutral comment (optional: add all the comments above) (note: no prefix here)

The important things:

  • use the prefixes only once (!) per feature, fix etc…
  • extended description in comments (starting with second line) won’t be parsed to add new changelog items (but to mark a “breaking change” if any).
0reactions
creativemind1commented, May 17, 2020

Oh wow thanks 😃

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found