Request access to new GitHub issues features
Refs: https://github.blog/changelog/2024-10-01-evolving-github-issues-public-preview/
I'd like to add the nodejs org to the waitlist. I think sub-issues and issue types will be very useful to us.
Here's a TL;DR:
-
Issue Types: https://github.com/orgs/community/discussions/139933 - Instead of labeling issues as “Feature Request” or “Bug” (which we don’t have), GitHub will support a classification of issue types, alongside the traditional labels.
-
Sub Issues: https://github.com/orgs/community/discussions/139932 - Currently, we use tracking issues to manage different long-term tasks, however GitHub is introducing sub-issues, a way to open an issue that is a part of another issue.
I think sub-issues and issue types will be very useful to us.
Personally, I'm looking forward to:
- On long issues, selecting ‘load more’ will now fetch 150 events instead of 50.
🙂
I've heard that it fails to load repositories with more than 1000 open issues :(.
@mcollina Is there a public discussion about this? I wouldn't like block on rumors.
No I don't atm :(
The microsoft/typescript repo has more than 5k issues open and is enrolled in the feature: https://github.com/microsoft/TypeScript/issues?q=sort%3Aupdated-desc+is%3Aissue+is%3Aopen
Given with the precedent on microsoft/typescript repo with more than 5k issues, any concerns remaining with moving ahead on this?
IMO we should, before moving forward, decide what "Types" to add (if any), just so we are all aware.
Here are the default issue types:
Here are the default issue types:
I feel we should have some based on the core labels we have? Not sure Task and Enhancement make sense. Bug, Feautre, Docs, Tooling, etc make sense for me.
I just requested access.
They just released some new stuff: https://github.blog/changelog/2024-12-12-github-issues-projects-close-issue-as-a-duplicate-rest-api-for-sub-issues-and-more/
It's now enabled.
I opened https://github.com/nodejs/admin/issues/938 to discuss the issue types
