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.

Using branch name tags for Github issues

See original GitHub issue

Our project has simultaneous active development happening on multiple branches. For eg. at the time of creating the issue 2.8-release, feedback-gamification, browse-commons-via-app and gamification are active. Even the other branches in our repo are not exactly stale and would be merged in due course of time.

Sometimes it’s difficult to figure out which feature branch the issue is referring to. Moreover, external contributors won’t have any idea that the issue might be talking about a feature branch.

Can we have branch name tags mandated for our Github issues? This would also make finding issues for a particular feature branch easy.

We can have this guideline added in the issue template if others agree to this proposal. 😃

Issue Analytics

State:
Created 5 years ago
Reactions:1
Comments:8 (6 by maintainers)

Top GitHub Comments

1reaction

misaochancommented, Jun 25, 2018

I’m good with the branch-* labels, and it’s a good idea to have that as a prefix IMO 😃. I would request all collaborators to help keep on top of these labels and remove them when we are done with the branches though, to prevent cluttering.

1reaction

nicolas-raoulcommented, Jun 25, 2018

Sorry I misunderstood the whole issue! I guess branch-2.8-release is not needed as we already have pre-release? I created two branch-* labels for the main branches we have currently.