Providers

Patchmill connects repository work to host providers and Pi runtime providers.

Supported issue-host workflow

Patchmill issue workflows need provider access for reading issues, applying labels, posting comments, and creating or updating pull requests.

Supported host paths include:

• GitHub through the gh CLI.
• Forgejo or Gitea through the tea CLI.

GitHub setup

For GitHub repositories, authenticate gh before running Patchmill commands:

gh auth status

Then configure Patchmill with the provider and repository details used by your project. The github-gh provider uses your active gh authentication context and does not support named logins.

Forgejo and Gitea setup

For Forgejo or Gitea repositories, configure a named tea login before running Patchmill commands:

tea login list

Use the configured login name when creating disposable demo repositories or configuring host access. Named-login overrides, including PATCHMILL_HOST_LOGIN, only apply to providers with named-login support such as forgejo-tea; github-gh ignores them.

Runtime Pi authentication

patchmill auth configures or repairs repo-local Pi provider authentication under .patchmill/pi-agent. Run it after provider credentials, model selections, or local runtime settings change.

Issue-host authentication remains separate: use gh auth login for GitHub and tea login configuration for Forgejo/Gitea access. patchmill auth only manages Patchmill’s repo-local Pi provider state.

Validate provider access

Run the doctor command after provider changes:

patchmill doctor

The doctor command is read-only and reports host access, labels, configured skills, runtime access, and local path status.