Define issue types for the `nodejs` org
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- github
- Domain
- devtools
Research direction
Read the context in admin issue #921 and review the organization issue-type settings linked in this issue. Determine and document the agreed set of issue types, including each name, description, color, and private-repository setting; completion requires agreement on the organization-wide configuration.
Written by the indexing model from the issue text.
Description
Now that we have access to the new GitHub issues features (https://github.com/nodejs/admin/issues/921), we should decide on the set of issue types that we want for the org.
By default, there are three: Task, Bug and Feature.
We can create a maximum of 25 issue types.
Issue type fields are: name, description, color (selected from a fixed list of 8 colors), and "private repositories only".
The main differences between issue types and labels are:
- An issue can only be assigned to a single type.
- Issue types cannot be customized per-repository.
Owners can see and edit the settings here: https://github.com/organizations/nodejs/settings/issue-types
- Dominant language
- JavaScript
- Stars
- 202
- Forks
- 183
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nodejs/admin
-
tsc-agenda
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
Difficulty 1/5 Under an hour Newbie friendliness 35/100
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100