7 min
Pin repositories as context
Pin a GitHub repository to a workflow or a chat. The agent starts every run with it.
5,000 free credits to start.
- 01
Find the repository the agent keeps looking up
Read a few runs and notice which codebase the agent reaches for every time. The service it reviews, the repository whose conventions it checks. That is the one worth pinning.
- 02
Pin it as an integration resource
A pinned resource scopes a connection to one repository. The pin carries the connection with it, so credentials stay at the network layer.
- 03
Attach it to the workflow or chat
A pinned repository is available in the sandbox on every run. The agent clones it with the in-sandbox git credential helper and starts from the code.
- 04
Use pinning to narrow reach
A workflow pinned to one repository has a smaller surface than one that can read the whole organization. Its prompt gets shorter as well.
- 05
Put stable facts in the prompt
Each run starts fresh. Escalation rules, naming conventions, and schema notes belong in the prompt so every run has them from the first step.
Keep going
Next guides
10 min
Run your first workflow
Describe a task in plain words, give the agent one tool, and read the run. Ten minutes from an empty workspace to a transcript you can read end to end.
12 min
React to GitHub events
Start a run the moment a pull request opens, a build finishes, or a tag lands. Filter down to exactly the events you want.
9 min
Share with your team
Hand a workflow to the people who need it. Four roles decide who may view, run, or edit. Every run leaves a transcript of what happened.
Templates
Put it to work
Templates that use what this guide covers.
Engineering
Pull request reviewer
Reviews every pull request against your conventions and leaves inline comments only where it found something concrete.
Engineering
Release notes writer
Turns a new tag into release notes grouped by theme, publishes a draft release on GitHub, and files a changelog entry in Notion.
Engineering
Incident postmortem drafter
Rebuilds the incident timeline from Slack and GitHub, names the likely change, and drafts the write-up in Notion.
Try it in your workspace.
Start free, connect a tool, and write the first prompt in plain words.