Am I missing the point or is there no “resolved” status in github?
having status open/closed means there is no workflow to the bugs – this is a bit of a let down.
or is it there but i’m just not seeing it?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Am I missing the point or is there no “resolved” status in github?
having status open/closed means there is no workflow to the bugs – this is a bit of a let down.
or is it there but i’m just not seeing it?
I can emulate the states of an issue by using the labels. Label a issue as “resolved” should everybody inform, why the issue is closed.
You are right, when you say, that there is no workflow defined by github, but using the labels gives you the opportunity to work, like there is the workflow you want, even if this means, that you have to take care about the consistency yourself (e.g. closing a “blocked by other issue” with “resolved” feels wrong as long as the other one is open).
You can add as many labels as you want to an issue, for example “critical” and “bug”. If there are dependencies, I suggest to add a link to the corresponding issues in the issue description.