> ## Documentation Index
> Fetch the complete documentation index at: https://docs.maia.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting Git errors

export const action_0 = "using Git actions in Maia"

export const maia_team = "Maia Team";

export const designer = "Designer";

export const maia = "Maia";

This guide lists and explains some common error messages that you may encounter when {action_0}. Where applicable, it also explains how to resolve the underlying issue. After following the steps to resolve an issue, if the error persists, raise a [Support ticket](https://support.matillion.com/). For more information about Support tickets, read [Getting support](/docs/guides/getting-support).

If you encounter an error that you think we should add to this guide, contact our Support team to let us know.

***

## "Something went wrong" when merging changes into a branch

This error message may appear if there are uncommitted changes on the branch that you are trying to merge changes into.

To resolve this issue:

1. Open the branch that you want to merge changes into.
2. In the branch menu, click **Commit changes**.
3. Go back to your original branch and commit any uncommitted changes.
4. Merge the changes into your chosen branch.

***

## No commits are available to push or publish, even though local commits exist

This can happen if {maia_team} has already pushed some or all of your local commits automatically while you were working, for example while completing tasks on your behalf. As a result, when you open **Push local changes**, {designer} may show fewer commits in the **Changes** count than you expect, because those changes have already been sent to the remote repository.

To resolve this issue:

1. Click **View commit history** to check whether the commits you expected to push have already been pushed to the remote repository. A blue arrow next to a commit hash indicates that the commit hasn't been pushed yet.
2. If the commits have already been pushed, no further action is required.
3. If you still have local commits that haven't been pushed, refresh the page and open **Push local changes** again, as the Git status shown in {designer} may be out of date.