Updated issue triage guidelines

[shilman]

Issue: #733

What I did

@tmeasday and I sat down and reworked the issue labels in the Storybooks repo. This change summarizes the changes we made. Separately we will propose some guidelines around closing issues that have gone stale, etc.

How to test

N/A

[tmeasday]

@shilman I think this branch is messed up, I don't see any changes

[shilman]

@tmeasday sorry my bad. fixed!

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (master@a9944e1). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master    #1024   +/-   ##
=========================================
  Coverage          ?   12.51%           
=========================================
  Files             ?      196           
  Lines             ?     4458           
  Branches          ?      713           
=========================================
  Hits              ?      558           
  Misses            ?     3269           
  Partials          ?      631

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a9944e1...674d6e2. Read the comment docs.

[tmeasday]

Looks good--want to add a description of what maintenance and greenkeeper mean too?

[ndelangen]

I think a label feature / change request might be more descriptive.

[ndelangen]

merged to master or released?

[tmeasday]

I think merged myself. Otherwise we need another label fixed or the like and we mentally have to ignore fixed issues. I appreciate users might not find an issue that has been closed but not yet released however.

[tmeasday]

Although maybe it's easier for us to ignore fixed issues, and we can use them to construct a meaningful changelog. I change my vote ;)

[ndelangen]

Good work!

[usulpro]

Could we add a description or clarify use cases for labels:

• do not merge / in progress. Is it different or should we left only one of them?

• ready

• needs review

does documentation include cases when we need documentation? And how should we handle situations when merging PR which adds a feature but does not document it. Should we keep the documentation label on this merged PR and remove it as soon as it adds to documentation?

One more not related to this PR but possible worth to discuss. Should we ask people to add [prefix] with area/type label when they submitting an issue/PR since they can't add labels themselves?

[shilman]

@usulpro Those are all great points. I'm going to merge this now and will follow up on the status-related labels in a separate PR.

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 674d6e2. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 1 target

• nx run-many -t build --parallel=3

---

Sent with 💌 from NxCloud.