Backlog -> In Progress -> Ready For Review -> Done
Issue stages
| Column | Description |
|---|---|
| Backlog | Tasks and ideas that are queued for future work but not yet started. Issues here are prioritised top down, and ready to be pulled to In Progress when capacity allows. |
| In Progress | Work that is currently being actively worked on. Items move here when a developer starts tackling them. |
| Ready for review | Completed work that’s ready for Stuart to review, test, and document. This signals handoff for quality assurance and documentation before final completion. |
| Done | Completed and shipped work that has passed review, testing, and documentation. Only Stuart should move issues to Done. |
| Needs Follow-up | Tasks that have been started but are blocked or need additional information before they can proceed. This is essentially a “blocked” or “waiting” state. |
PR-based workflow
All contract developers should follow this PR-based workflow:- Create Pull Requests - All code changes must be submitted as PRs, not merged directly to main
- Request Review - Tag @ninjaparade for code review on each PR
- Review & Merge - @ninjaparade will approve and merge the PR directly. If there are changes requested, the developer should address them and re-request review.