This is the current map for people looking at the issue queue for the first time.
The full queue is useful, but it is too large to scan cold. Start with one of the tracks below, comment on the target issue before opening a pull request, and keep the patch small. Maintainers use Forgejo internally; first-time contributor review happens on GitHub.
Refreshed May 15, 2026:
Start here this week
Pick one of these before browsing the full list. They are small, current, and tied to the public adoption path for @bilig/headless.
Best first code and test tasks
Use these if you want one focused test and a small diff:
Best first service and example docs
Use these if you want to add a copy-pasteable WorkPaper recipe:
Agent, MCP, and evaluation tasks
Use these if you care about coding-agent workflows, MCP setup, or spreadsheet accuracy evaluation:
Before opening a PR
A useful claim comment is:
I can take this.
Plan:
- files I expect to touch:
- validation command:
- question or assumption:
Then keep the PR focused:
- Use TypeScript examples, not pseudocode.
- Prefer public
@bilig/headless exports.
- Include the command you ran and the expected readback or output.
- Link the issue in the PR body.
- Open the pull request on GitHub.
Contributor docs:
This is the current map for people looking at the issue queue for the first time.
The full queue is useful, but it is too large to scan cold. Start with one of the tracks below, comment on the target issue before opening a pull request, and keep the patch small. Maintainers use Forgejo internally; first-time contributor review happens on GitHub.
Refreshed May 15, 2026:
first-timers-onlyissues.Start here this week
Pick one of these before browsing the full list. They are small, current, and tied to the public adoption path for
@bilig/headless.Best first code and test tasks
Use these if you want one focused test and a small diff:
Best first service and example docs
Use these if you want to add a copy-pasteable WorkPaper recipe:
Agent, MCP, and evaluation tasks
Use these if you care about coding-agent workflows, MCP setup, or spreadsheet accuracy evaluation:
Before opening a PR
A useful claim comment is:
Then keep the PR focused:
@bilig/headlessexports.Contributor docs: