githubnext/chopinPublic

Let's compose rich plans together

Enable external contributions would be helpful

questiontriage/human-response
RA

I did not notice that it was limited (might be an extra case for #149) and got a PR ready for the initial setup and onboarding improvements:

https://github.com/githubnext/chopin/compare/main...rajbos:github-vnext-chopin:main?expand=1

<img width="1439" height="755" alt="Image" src="https://github.com/user-attachments/assets/c6c717f5-67d2-4ed8-bbe4-b1d58e630a68" />

Let me know if you want it 😄

  1. lavaman131referenced this in Support device-flow sign-in for local instances with persistent credentials #157last month on GitHub

  2. MaggieAppletonreferenced this in Triage issues and acknowledge external contributors with Codex #316last month on GitHub

  3. github-actions[bot]botreferenced this in Add an `CONTRIBUTING.md` to help people #149last month on GitHub

  4. github-actions[bot]botadded label questionlast month on GitHub

  5. github-actions[bot]botadded label triage/human-responselast month on GitHub

  6. Automated triage here—thanks for explaining that you already prepared setup and onboarding improvements, and sorry your offer has waited. I’m routing this to `triage/human-response`: whether external contributions are accepted and whether the offered work is wanted need a maintainer answer. This is related to #149’s request to document contribution expectations, rather than a duplicate of that documentation request.

    > Generated by [Issue triage](https://github.com/githubnext/chopin/actions/runs/37621759756) · ⊞ 18.4K · [◷](https://github.com/search?q=repo%3Agithubnext%2Fchopin+%22gh-aw-workflow-call-id%3A+githubnext%2Fchopin%2Fissue-triage%22&type=issues)

    <!-- gh-aw-agentic-workflow: Issue triage, engine: codex, model: gpt-6.1-sol, id: 37621759756, workflow_id: issue-triage, run: https://github.com/githubnext/chopin/actions/runs/37621759756 --> <!-- gh-aw-workflow-call-id: githubnext/chopin/issue-triage -->