Your customers file issues and your engineering work lives in pull requests. Squad reads new issues as feedback on their own, and an agent can start when an issue opens or a pull request merges, read either one, and write back an issue or a comment.
Connect
GitHub connects through a GitHub App install, not an OAuth consent screen.
Start the install
Click Connect on the GitHub card. GitHub’s install app screen opens.
Pick the account and the repositories
That screen asks which account or organisation to install Squad on, and which repositories it may access (all of them, or a list you choose).
Disconnect
Click Manage on the GitHub card, scroll to Danger Zone at the bottom of the page, and click Disconnect. Triggers stop, agents lose the GitHub tools, and the card drops out of Connected back into Discover.
Disconnecting also uninstalls the Squad app from your GitHub account. The installation disappears from your GitHub settings and Squad’s access to those repositories ends immediately. Connecting again means going through the install screen and the repository choice from scratch.
Getting issues into your feedback
Switch on the GitHub issues workflow from the By Squad tab on the Agents page. An issue in the repositories you scope it to is captured with its comment thread, turned into signals, and logged whether it captured, skipped or failed. No agent is involved.
Capture happens when an issue is opened and when it is reopened. So a three-year-old issue joins the moment someone reopens it, comment thread and all. Comments alone do not bring one in.
Leave the repository list empty for every repository the install covers.
Bot-authored issues are always skipped, because Dependabot and Renovate open issues continuously and none of them is a person reporting a problem.
An empty repository list covers every repository the install can see, private ones included. GitHub’s install screen offers All repositories, which also picks up any repository created later, so check what the install covers before leaving the scope empty.
Triggers
- Issue opened. An issue is opened in an installed repository.
- Pull request merged. A pull request is merged in an installed repository.
Both fire across every repository in the installation. Closed issues, opened pull requests and review comments are not triggers.
In a triggered run each one defaults to the issue or pull request that started the run. Neither brings an issue into your feedback. That is the GitHub issues workflow, which captures every issue in scope whether or not an agent asks for it. Both act on your repositories. Each connection is set to None, Read only or Read & write, and a triggered agent needs Read & write to use these two. Chat is the exception, since it gets write access to every connected integration.
A worked example
Build an agent triggered on Issue opened. It reads the issue, checks the description against recent signals to see whether customers have hit the same thing, and comments with how many customers, how recently, and which insight it belongs to. Engineering gets the demand context on the issue itself, before anyone picks it up.
Limits
Squad reads issues and pull requests. It does not read code, files, diffs or commits. The two triggers are the only GitHub events available to an agent. Repository access is set in the GitHub install, not in Squad.
The issues workflow starts from the moment you switch it on and nothing before that is backfilled in bulk. An older issue still comes in when someone reopens it. Pull requests, discussions and releases have no workflow. 
