Connect GitHub by installing the Maximal GitHub App.

Install

A workspace admin opens Connectors, chooses GitHub, and installs the app on the organization or the repositories Max should see. GitHub hands the installation back to Maximal, which stores it with your workspace only.

Access

Max exchanges the installation for short-lived tokens limited to the repositories you granted. Removing the connector in Maximal stops Max from using it; to revoke the access itself, uninstall or suspend the app in GitHub.

What Max does with it

Opens a pull request only as a remediation: a revert of the commit behind an incident, or a targeted change to the configuration file you name. Every pull request needs a human approval first, and reviewing and merging it stays with your team.

Linking deploys to commits

Max can only revert a commit it can name. Have your deploy pipeline tag the Lambda function, or each ECS task definition revision, with maximal:git-commit (the full 40-character SHA) and maximal:git-repo (owner/repo). Max offers a revert pull request when an alarm follows a tagged deploy and there is no alias to roll back.

Naming the file Max may change

Tag the Lambda function, the ECS task definition, or the CloudWatch alarm itself with maximal:git-repo and maximal:config-file, the repository path of the file that configures the resource (for example infra/rds.tf), and optionally maximal:git-branch. When nothing can be rolled back, Max can draft the smallest change to that one file. It never edits any other file.

After you merge

Opening the pull request changes nothing. Max waits for the merge, then checks that the alarm recovers. A pull request closed without merging, or left open for a day, escalates the incident to your team; a stale one is closed.