Connect GitHub

When you connect GitHub, the agent can read your plugin's code, search your issues and file new ones. You decide which repositories it can reach and which actions need your approval.

Before you start

You need:

• A GitHub account that can install apps on your repositories, or on your organization.
• The repositories for your plugins and themes.

Connect GitHub

1. In Repile, open Settings, then Integrations under Agent tools.
2. Click GitHub.
3. Under Repile GitHub App, click Connect GitHub.
4. On GitHub, install the app and pick the repositories the agent may reach.
5. Go back to Repile. The card shows Installed on your account and the repositories you picked.

To give access to more repositories later, click Add repositories.

Issues the app files show as posted by repile[bot]. Your workspace can only reach the repositories it connected.

Choose a default project

Under Issues, set Default project. Agent threads for a repository that has no project of its own start there.

Repile follows every project whose checkout has a GitHub origin remote. Those repositories use their own project.

Choose what the agent may do on support tickets

Under Support tickets, set Ticket agent GitHub actions:

• Ask me first is the default. The agent asks before every issue, push and pull request.
• Create issues automatically; ask before pull requests lets the agent file issues at once. Pushes and pull requests still need your approval.
• Do everything automatically shows no approval card for issues, pushes or pull requests.

The automatic modes only act without a card after a person on your team has typed a message in the ticket thread. A thread that started from customer mail or a forum post shows a card for every write until a teammate writes in it.

Merging a pull request always asks first in a support ticket thread, in every mode.

When the agent files an issue

On a support ticket, the agent first searches the repository for an existing issue. In the automatic modes, it files a confirmed bug only when that search finds no match.

When an action needs approval, a card shows in the thread with the repository, the action, and the title and body or branch. Click Approve to run it. Click Decline to stop it. The agent gets the result either way. Cards open one at a time, and a card you do not answer expires after one hour.

Protect your customers on public repositories

On a public repository, Repile refuses an issue or pull request that contains:

• A link to a site other than GitHub, WordPress.org, or the repository's or owner's own website.
• An email address.
• A help desk ticket reference.

Repile also refuses an issue on a public repository that mentions Pro until the agent confirms the bug is in code that repository ships. A bug in Pro-only code goes on the Pro repository.

Ticket agents commit as Repile Agent, with no AI attribution in commit messages.

What else you get

• A GitHub panel with Issues and Pull requests tabs across your repositories, with a repository filter and a New issue form.
• Send agent on an issue, or Review with agent on a pull request, starts a thread in the repository's project.
• Type @ or # in any message box to attach an issue or pull request. The agent gets its title, body and state.

Troubleshooting

• "Not installed": click Connect GitHub and finish the install on GitHub.
• The agent cannot see a repository: click Add repositories and pick it on GitHub.
• A git push fails in a ticket thread: this is expected. In ticket threads, plain git gets a read-only token, so pushes go through the agent's push tool and its approval card.
• "GitHub did not accept the sign-in.": click Sign out, then Sign in with GitHub again.