Features

Every feature of the issue assistant has a page of its own, which opens with a picture of how it works. How it works shows how the workflows fit together, and Configuration has every setting.

• The first analysis: the likely cause with links to the code, what to try and what is missing, in the reporter's language.
• The life of an issue: labels say where an issue stands, and the assistant keeps what its comments promise, without AI.
• Priorities, owners and issue types: an analysis can set a priority, assign an area's owners and follow the kind with an issue type.
• Waiting periods, exemptions and old threads: a reminder after 15 days and the closing after 30, or your own days, with exemptions and locks.
• Duplicates: a sure duplicate closes three days after its notice unless someone objects; others are suggestions.
• Related repositories: also searches the issues of projects that share your users, and says when an issue may belong there.
• Questions in Discussions: a first answer to a new question, with the same AI and the same checks, never marked as the answer.
• Slash commands: steer the assistant from the issue, such as /assistant again or /assistant ask <question>.
• From the fix to the release: a fixed issue stays open until a release ships the fix, then closes with a link to it.
• What the AI reads: each task reads what it needs and no more, and a first analysis learns from the maintainers' corrections.
• Languages: fourteen catalogs for the reporters, and a folded summary for maintainers who don't read their language.
• Limits of the AI runs: no stranger can run up the bill: the runs that others than the maintainers start are limited.
• What one run may cost: each run stops at its turns and its dollars, and the summary of its job says what it cost.
• What the sweep tells the maintainers: every morning what waits on whom, if you want in a pinned issue, and once a month how well it did.
• When GitHub fails: a rate limit, a server error or an incident never changes what the assistant posts.