Starter Issues

June 3, 2026 ยท View on GitHub

This page is the stable contributor on-ramp for small public bilig tasks. It intentionally stays short: GitHub's good first issue, first-timers-only, and help wanted labels should point to work that is current, scoped, and credible for someone opening the repository cold.

Current starter queue as of June 3, 2026:

  • 0 open good first issue issues.
  • 0 open first-timers-only issues.
  • 0 open help wanted issues.
  • 0 starter issues are code or test tasks.
  • 0 starter issues are focused docs or integration transcript tasks.
  • 0 starter issues are currently under active review.

Start Here This Week

There are no open first-patch issues right now. Browse the full issue list or open a Discussion with a small agent, workbook import/export, or formula readback gap that you can reproduce.

Code And Test Starters

No code or test starter issues are currently open. Open a scoped code/test ticket before the next contributor push if the queue should include one.

Integration Docs Starters

No integration-docs starter issues are currently open.

Claim A Starter Issue

Comment on the issue before opening a pull request. If the issue is unassigned, a maintainer can assign it to you and keep the scope reserved while you work. If it already has an assignee, pick another starter ticket or ask whether the current assignee still wants help.

For a first patch, keep the pull request focused on the issue's acceptance proof. Include the command you ran, mention the issue number, and open a draft pull request early if any requirement is unclear. The new contributor guide gives the shortest setup, code-map, and first-time command checklist. Read CONTRIBUTING.md before opening the pull request.

Useful filters:

GitHub surfaces issues labeled good first issue in contributor discovery paths, per GitHub's label guidance, so starter tickets should stay genuinely scoped and current. Do not use that label for cross-cutting formula, import/export, or runtime changes that require broad architectural context.

Use first-timers-only only for issues that are ready for someone making their first contribution to this repository. Those issues should name the expected files, a copyable validation command, and a narrow acceptance proof in the issue body.

Add help wanted only when an external contributor can make progress without private context or maintainer-only systems.