Skip to main content
Fix It For Me is currently in Beta. If you would like early access, please reach out to us.

​
Overview

Fix It for Me allows Macroscope to automatically create branches, commit code changes, and open pull requests in your GitHub repositories. When a user replies to a Macroscope review comment requesting a fix, the system creates a new branch, applies the fix via an AI agent, and opens a pull request with the changes.

​
Fix It For Me Steps:

  1. User replies to a Macroscope review comment requesting a fix, or asks Macroscope to create a PR from Slack
  2. Macroscope creates a new branch
  3. The Macroscope agent generates and commits the fix on that branch
  4. Macroscope opens a pull request. If generated from a Github review comment, the base of the PR will be the feature branch of the originating PR. If generated from Slack, the base of the PR will be your main development branch.
  5. GitHub Actions and CheckSuites run on the new PR. If any of these fail, Macroscope will attempt to automatically make fixes and commit them to the branch until all the actions pass.
  6. If the base of the PR is a feature branch, Macroscope will attempt to auto-merge the PR back to the base branch. This will only happen if you have the auto-merge Macroscope setting enabled and all checks pass. Any Macroscope PRs against your main development branch will always need to be manually merged.

​
GitHub Branch Protection Configuration

As a general rule, you should not need to add any extra branch protection rules to your Github configuration for Fix It For Me to work. As long as you have general protection rules on your main and deployment branches, you can keep all of those as they are. Macroscope will not write directly to any main branches, and should operate the same as any other developer on your team. For Fix It For Me to work, Macroscope needs the ability to create new branches and to push changes to those branches. Branches created by Macroscope will always follow the naming pattern of macroscope/*/**. If you have rules that apply to all branches, including restrictions to how changes are pushed, you may need to update them to exclude branches generated by Macroscope. This includes settings such as “Require a pull request before merging” and “Block force pushes”.

​
GitHub Actions and Check Runs

Fix it For Me relies on your already configured Github Actions and CheckSuite Runs to determine if the change is free of issues and safe to be merged. This allows us to use the same safety checks for Macroscope PRs that you already use for any other work the team creates. In some cases, you may want to limit which actions or CheckSuites run on Macroscope PRs to reduce latency or cost. For example, you may want to not run certain actions that take a very long time intended to protect merging into the main branch, as Macroscope would wait for that action to complete every time before making further fixes or merging the fix into the originating branch. If you want to limit this, you can add Github rules for any branches generated by Macroscope (following the macroscope/*/** naming convention), and select the specific set of actions you want to run in these cases.

​
Generated Code

If you have auto-generated code in your repo, Macroscope may not be able to correctly run the script to re-generate that code based on the changes it makes. To allow Macroscope to still handle these cases automatically, make sure that any tests around your generated code include the code diff of the expected code in the output of the test. If Macroscope sees that diff in the test output, it will automatically apply that diff and create a new commit to try and resolve the errors. See the example test below.

​
Test Example

name: Protobuf generated code up-to-date

on:
  push:
  pull_request:

jobs:
  protobuf-gen-check:
    runs-on: ubuntu-latest

    steps:
      - name: Checkout
        uses: actions/checkout@v4

      - name: Setup Go
        uses: actions/setup-go@v5
        with:
          go-version: "1.22"

      - name: Install protoc plugins
        run: |
          go install google.golang.org/protobuf/cmd/protoc-gen-go@latest
          go install google.golang.org/grpc/cmd/protoc-gen-go-grpc@latest

      - name: Regenerate protobuf files
        run: |
          protoc -I=proto \
            --go_out=. \
            --go-grpc_out=. \
            proto/*.proto

      - name: Fail if generated files changed (shows diff)
        run: git diff --exit-code