Proposal: Contributor-Focused Issue Triage for Available Work

[UtkarshAnandd]

Context

While going through the Music Blocks issues and PRs, I noticed that it can be difficult for a new contributor to answer a simple question:

Which issue can I actually start working on right now?

Music Blocks already has several useful systems around this:

• Structured issue templates
• Issue labels such as Issue-Bug, Issue-Enhancement, Issue-Testing, etc.
• Good first issue for newcomer-friendly work
• Milestones such as Port Ready, Migration, and Future
• The existing Pull Request Dashboard (Pull request dashboard #8323) for tracking open PRs and identifying who needs to act next

After looking through the existing PR Dashboard implementation, I don't think we should duplicate or replace it. It already does a good job of handling the PR → review → merge part of the workflow.

I think there may instead be a gap one step earlier:

Issue → Contributor

Proposal

I'd like to explore a lightweight Contributor Issue Triage system that helps contributors discover issues that are currently available to work on.

For example, it could distinguish between:

🟢 Available

An open issue that has:

• No assignee
• No active linked PR
• No Issue-Duplicate or Issue-Wontfix label
• No known blocking condition

If maintainers have already marked it Good first issue, it could be highlighted as a newcomer-friendly opportunity.

🟠 Already Active

An issue where someone is already assigned or an active PR exists.

Instead of encouraging another contributor to start duplicate work, the system could point them toward the existing PR.

🟡 Needs Triage

Issues that need maintainer attention before someone should start working on them, such as explicitly blocked or unresolved issues.

Important scope boundary

This would not be another PR Dashboard.

My current understanding is:

             Open Issues
                  │
                  ▼
       Contributor Issue Triage
                  │
          Contributor picks work
                  │
                  ▼
              PR created
                  │
                  ▼
       Existing PR Dashboard #8323
                  │
          Review / CI / Conflicts
                  │
                  ▼
                Merge

[UtkarshAnandd]

I'd especially appreciate a quick review from @vyagh @Ashutoshx7 @walterbender since this touches the existing issue/PR workflow.

I'm mainly looking for feedback on the problem and scope at this stage — whether this fills a real contributor gap, and whether the proposed separation from the existing PR Dashboard (#8323) makes sense.

I'm happy to adjust the proposal before implementing anything.

[vyagh]

The proposal is good. I like how you have described the complete flow and the problem. I think we can also pin this on the issues tab when it's complete.

[UtkarshAnandd]

Thanks Vyagh! Glad the overall flow makes sense.
I’ll start by validating the approach against a few real issues and then build a small read-only prototype that surfaces existing PRs, recent activity and other relevant context for contributors.

Once the prototype is working, I’ll share it here for feedback before integrating it into the Issues workflow. And yes, pinning it on the Issues tab once it’s complete sounds great. 👍

[vyagh]

any progress on this? or any help you need ?

[Ashutoshx7]

yup @UtkarshAnandd lmk if there is any we can help

[UtkarshAnandd]

Thanks both! Yes, I’ve made some progress on this. I’ve built the initial issue-context prototype and added tests, and I’m currently validating the workflow and cleaning up a couple of Git/worktree issues before I share it for feedback.

I’ll post an update here once I have the prototype in a clean, reviewable state. I may reach out if I get stuck on anything where your input would help. Appreciate it! 🙌

[UtkarshAnandd]

[UtkarshAnandd]

Thanks @vyagh and @Ashutoshx7 ! I’ve made some progress on this and wanted to share a quick snapshot of where things currently stand. The initial issue-context prototype and tests are in place, and I’m now validating the workflow and polishing a few things before sharing it for feedback. Attaching a screenshot for some context

[Chaitu7032]

After analyzing the topic, it looks like we can automate the Contributor Issue Context feature completely without asking the contributors to run the script themselves.

The script for collecting and formatting the required information will be implemented by issue-context.py and GitHub Actions will run it automatically when there is something to process regarding that issue or related PRs. And the resulting context will be updated right in the issue.

From the perspective of a contributor, this workflow will be extremely easy:

Open the issue → Check Contributor Context → Analyze the previous works and discussions → Decide if you want to contribute to it → Create a PR.

This will make it really helpful for new contributors who do not have to know anything about the script or even how to use the terminal to get the necessary information while working with the issue.

I think it will also fit nicely with the existing PR Dashboard #8323 because this approach will mostly focus on what should be done before contributing , and the existing dashboard will continue to work with the PR workflow.

this is form my perspective as this looks interesting