Skip to main content
With Inbound Webhooks & Triggers turned on, your character can pick up work straight from GitHub. When someone mentions it in an issue, a pull request or a comment, a Studio session starts, the character plans the work, and you review it in Studio.

How it works

1

Someone mentions the character on GitHub

For example, a comment on an issue says “@luna can you fix this?”. The mention is @ followed by the name in the character’s dashboard link (labs.aurinfer.com/luna), or the character’s name without spaces.
2

AurInfer checks the event

The person must have write access to the repository, or be on your allow list. Bots are ignored, so the character never answers itself.
3

A session starts

The session starts in Plan mode with Ask before committing, so nothing is changed or pushed without you. It works on a branch for the issue, or on the pull request’s own branch, and uses the character’s Primary Coding Engine.
4

The character posts a link

If Post Progress Comments to GitHub is on, the character comments on the issue or pull request with a link to the session.
5

You review it in Studio

The session shows up in your Studio list as Awaiting Approval once the plan is ready. Approve the plan, then commit as usual. See Working in a Session.
Sessions started from GitHub belong to the character’s owner, and they use the owner’s credits and plan limits.

Before you start

  • The character needs the GitHub integration set up.
  • Start at least one Studio session in the repository first. The character only answers events from repositories it has worked on in Studio.
  • The character’s owner needs GitHub access to the repository, through the GitHub App or their connected GitHub account. See GitHub Access.

Set it up

Open Coder → Settings and find Inbound Webhooks & Triggers.
If the repository is covered by your AurInfer GitHub App installation, GitHub already sends its events to AurInfer. You don’t need to add a webhook on GitHub.
1

Turn on Inbound Webhooks & Triggers

Switch on Inbound Webhooks & Triggers.
2

Choose the options

Pick the Trigger Events and any of the options below.
3

Save

Click Save Webhook Settings.

Options

New issues, new pull requests and comments only start a session when they mention the character. Adding a label to an issue starts a session without a mention, if Issues Labeled is selected. Use Required Issue/PR Label so that only your chosen label does this.
A label such as aurinfer makes a good switch: add it to the issues you want the character to handle, and set it as the Required Issue/PR Label.

Recent deliveries

Under the options, Recent deliveries shows what GitHub sent in the last 24 hours and what came of it. Click Refresh to update the list. The number of sessions GitHub can start is limited per repository each hour, and in how many can run at once, so a busy repository can’t start sessions without end.

Troubleshooting

With a repository webhook, check the webhook’s Recent Deliveries on GitHub. A red result usually means the Payload URL or the secret doesn’t match. With the GitHub App, make sure the App installation covers the repository and is linked to the character owner’s account.
Read the reason under the delivery. The most common ones are a missing mention, a missing required label, a sender without write access, or a repository the character hasn’t worked on in Studio yet.
When Integration Enabled is off in Workflow Settings, GitHub events don’t start sessions. Turn it back on and click Save Settings.