2 – GitHub Configuration

Details

The Details page provides Dosu with additional context about your repository and lets you set deployment metadata.

Issues

The Issues settings determine how Dosu behaves on the repository’s issues.

Note: If issues are disabled for the repository, Dosu will show a message and skip this section.

Agent Reply Behavior

This setting controls when Dosu responds.

Auto-Label Issues

These settings determine whether Dosu auto-labels issues and which labels it can use.

Dosu will only consider the labels you select. If a label is not selected, Dosu will never apply it.

Dosu chooses labels based on the issue title, description, and how similar issues were labeled in the past.

Best practices:

Stale Bot

These settings control Dosu’s smart stale bot.

If enabled, Dosu posts a stale comment summarizing issue activity, applies the stale label, and closes issues after the close window. Configure:

Encourage Issue Voting

This setting determines if Dosu applies a 👍 to every new (non-bot) issue.

Pull Requests

Pull Request settings determine how Dosu behaves on PRs. These features rely on GitHub App pull request permissions so Dosu can read PR metadata and file changes and apply labels. Dosu does not open or merge PRs.

Auto-Label Pull Requests

These settings determine whether Dosu auto-labels pull requests and which labels it can use.

Dosu considers the PR title, body, diff summary, and changed files when selecting labels. Label selection works the same way as Auto-Label Issues.

Add LGTM Label

When enabled, Dosu adds an LGTM label after a user with write access approves a review.

If the label doesn’t exist, Dosu will create it automatically.

Add Size Labels

When enabled, Dosu labels PRs by diff size (for example size:XS, size:S, size:M, size:L, size:XL, size:XXL).

Size is based on total line changes, excluding auto-generated files detected via .gitattributes.

Self-Documenting PRs

When enabled, Dosu updates your published documentation in your Dosu knowledge base and posts a summary comment on the PR. Dosu does not open PRs to modify repository files.

You can configure which file paths Dosu monitors for documentation changes. If specified, the stale documentation check only runs when files matching the configured paths are modified. Use glob patterns like src/**, docs/**/*.md, or specific file paths. If no paths are specified, all file changes trigger the check.

To manually trigger a documentation staleness check on a pull request, comment /dosu-refresh on the PR.

Discussions

Discussion settings determine how Dosu responds on GitHub Discussions.

Note: If Discussions are disabled for the repository, Dosu will show a message and skip this section.

Agent Reply Behavior

Same options as Issues:

Included Categories

When Auto Draft or Auto Reply is enabled, choose which discussion categories Dosu is active in.

By default, Dosu is active in Q&A and Questions.