GitHub

Access code repositories, pull requests, and issues.

What it does

Works with repositories, issues and pull requests. Mostly useful for technical delivery projects and for agents that watch a codebase.

What you need

An account with GitHub that you are entitled to authorise, and a moment in a browser. You do not need an API key: connecting sends you to GitHub's own sign-in and consent screen, and what comes back is an authorisation rather than a password. RAiN never sees your password, and the authorisation is held by our integration provider on our instructions — see the Integrations & Connected Accounts notice for what that means.

Connecting it

Connections belong to one project. A system built for one client never acts on another client's account, and a package handed to a business runs on theirs — so the same integration is connected again, separately, for each project that needs it.

Open the project and stay on the Visual Editor tab.
Open the Tools & Integrations rail on the right.
Find GitHub and press Connect.
Authorise in the window that opens, then come back. The rail will show it as connected.

The consent link is good for about twenty minutes. If you leave it and come back tomorrow, press Connect again rather than reusing the old tab.

To stop it, press Disconnect. That ends this project's access immediately. You can also revoke it from GitHub's own security settings, which works even if you never open RAiN again.

What an agent can do with it

66 actions are available once connected, 2 of which delete things and are marked where they appear. They appear in the tool list for this project only — a project that has not connected GitHub is never offered them.

Action	What it does
`github_add_a_repository_collaborator`	Add a repository collaborator
`github_add_assignees_to_an_issue`	Add assignees to an issue
`github_add_email_address_for_authenticated_user`	Add email for auth user
`github_add_labels_to_an_issue`	Add labels to an issue
`github_add_or_update_team_membership_for_user`	Add or update team membership for a user
`github_approve_workflow_run_for_fork_pull_request`	Approve a workflow run for a fork pull request
`github_check_if_pull_request_merged`	Check if pull request merged
`github_close_pull_request`	Close a pull request
`github_close_issue`	Close an issue
`github_commit_multiple_files`	Commit Multiple Files ⚠️ deletes things
`github_compare_two_commits`	Compare two commits
`github_create_a_blob`	Create a blob
`github_create_branch`	Create a branch
`github_create_a_commit`	Create a commit
…	and 52 more, all listed in the rail

Tick the ones an agent may use, or choose one in an Action step to run it exactly as written with no model involved.

A worked example

An agent watches a client's repository for dependency alerts and opens an issue summarising what changed and what it affects.

When it goes wrong

Rate limits. GitHub is strict. Keep the number of calls per run small.