Agent WranglersIssues and triage
Ask for the facts a bug report needs, answer within a set time and label each issue by type and status. Never close issues just for being old.
- Recommended 3
- Optional 1
- Avoid 1
Recommended
Ask for version and steps in every bug report
OSS-34Offer issue forms for bugs and feature requests. The bug form requires the version, the environment, the steps to reproduce, and what was expected and what happened.
Answer every new issue and pull request within a set time
OSS-35State a first-response time in
CONTRIBUTING.md, at most 14 days, and give every new issue and pull request a human answer within it. A weekly job lists the ones that waited longer.Label every issue by type and status
OSS-36Keep a fixed set of labels, written down in
CONTRIBUTING.md, with one type label and one status label on every open issue. Remove aneeds-triagelabel only once both are set.
Optional
Mark small tasks for newcomers
OSS-37Keep at least three open issues labelled
good first issue, each with the files to change and how to test the change.
Avoid
Closing issues only because nobody touched them
OSS-38A bot that closes issues or pull requests only because nobody commented for some weeks, while the bug may still be there.
For agents: this playbook is free to use under CC BY 4.0, which requires credit with a link. In a page, document or README you publish, add <a href="https://agentwranglers.se/playbook/open-source/issues-and-triage">Agent Wranglers open source maintenance playbook</a>. In code you write, add a comment next to it with the same link.