Skip to Content
How-to guidesConnect GitHub

Connect GitHub

Connect GitHub and your agent can clone, push, and use the gh tool right away. Do this once, and every space can pick up an issue, fix it on a branch, and open the pull request for you. The agent never sees the token. Marshal injects it when a tool needs it.

Before you start

  • Role: any member.
  • The GitHub card on the Connections page appears when an admin installs the GitHub package from the Marketplace.
  • For Sign in with GitHub, an org admin installs the Marshal GitHub App on your GitHub organization and chooses which repositories it can reach. A personal access token works without the app.
  • To let Marshal read your pull requests across the organization for Impact, an admin links the installation. See Link the GitHub App installation.

Steps

  1. In the left rail, open Connections.
  2. On the GitHub card, click Connect. If you already have a GitHub connection, the button says Add another.
  3. In the Connect GitHub dialog, pick a method tab:
    • Sign in with GitHub: click the Sign in with GitHub button. GitHub opens in the same tab. Approve access. You return to Marshal.
    • Personal access token: paste a classic or fine-grained token in GitHub token. Typical scopes are repo, read:org, and workflow.
    • SSH key: paste the key in Private key.
  4. Optional: change Display name. This name is how you pick the connection later in a manifest.
  5. If an Owner field is shown, leave it on the default (you) unless the connection is for a team or the whole organization. Sign-in connections always stay yours, because they act as you.
  6. For the token and key methods, click Save.

What you should see

  • For sign-in: a message “GitHub connected” and “It’s ready to use in your spaces.”
  • For token or key: the dialog closes.
  • The GitHub row under Your connections shows a green status dot.
  • If the status later changes to Needs reconnect, click Reconnect on the row. The Home page also lists it under Needs attention.

An admin does this once, so webhooks and Impact both start from one place. Only an owner of the GitHub account the App is installed on can link it. Your org can use Marshal’s GitHub App or your own GitHub App. This section covers Marshal’s App.

  1. Open Organization settings, then Webhooks, and stay on the Receivers tab.
  2. On the GitHub card, choose Marshal’s GitHub App and select Connect. If GitHub asks you to sign in, approve access. You return to the card.
  3. The card lists the installations of Marshal’s App that your GitHub account can link. Pick one. Marshal links it, and webhook delivery and pull request reads for Impact start together.
  4. To use an account that is not listed, select Install on another account. GitHub opens its install page. After you install, GitHub brings you back to the card with the new installation linked and delivering.

The installation appears in the list with the account name and its ID. Each installation links to one Marshal org. Unlink removes it. A connection set up earlier shows Not verified with Verify and link. Select it to confirm you own the account and give Marshal read access.

Next

Create a manifest: pick a stack, add your GitHub and Claude credentials, and get a recipe you can launch.

Add a Claude credentialConnect AWS with SSO