The GitHub App connects a selected repository to Omni Impact so you can publish reviewed source-file changes for your site's pages.
Install and select a repository
To set up GitHub, install the App, then choose the repository and the domain it serves.
- Open Apps, find GitHub App, and select Install.
- Complete the GitHub authorization and installation flow for the repositories you want to connect.
- Return to Connected and open Repository settings.
- Select the domain served by the repository, then select the repository.
- Check the mapped-page result. If no pages are mapped, crawl your domain and check that the repository contains your site's source.
The repository panel shows the selected repository, Publish mode, and Path prefix. Check those values before approving a change.
Review a file change
Publishing requires a page linked to its source file and a reviewed fix. If the file changed after your review, refresh it and review the updated fix before publishing.
In Improve, open your mapped page's AEO Engine recommendations and review the available fix. Select Publish to GitHub when the change is ready, then confirm the destination file in the confirmation prompt.
Pull request or direct commit
The configured publish mode determines whether your approval opens a pull request or commits to the repository's default branch.
| Mode | Result |
|---|---|
| Pull request | Omni Impact creates a branch and opens a pull request. The change is pending until that pull request is merged. |
| Direct commit | Omni Impact writes the approved file to the default branch. |
Follow your repository's review and deployment process. Opening a pull request is not the same as publishing the change on your live website. The result gives you a pull-request link when one was created.
Revert a GitHub change
Use Site Change History to review a successful GitHub App change and select Revert this change when available. The reversal depends on the original change's state and publish mode.
- A pending, unchanged pull request is closed.
- A merged change in pull-request mode opens a new revert pull request. The base branch is restored only after you merge that revert pull request.
- A direct-commit change is reverted on the original branch.
If the file or pending pull request changed after publishing, revert may be blocked. Review those later edits and resolve the change in GitHub before deciding what to restore.
When publishing is unavailable
Check that your GitHub App installation can access the selected repository and that your page appears in the mapped-page result. Reconnect if repository access was removed. Then review the fix again before publishing.
For a stale-file message, refresh and review the proposal again. For an uncertain result, inspect GitHub and Site Change History before retrying. Contact support if the connection remains blocked.