Skip to main content
This guide lists and explains some common error messages that you may encounter when using Git actions in Maia. 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. For more information about Support tickets, read 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.

​
”Files exceed processing limit”

This error message appears if the combined size of the files in your repository is too large for Maia to process. As a general guide, try to keep your total repository size under 100 MB. This is not a hard limit, so if you are close to it and still encounter this error, consider removing large or unnecessary files from the repository. Deleting the files and committing the change does not reduce the size of your repository. Git retains every version of a file in the commit history, so the files continue to count towards your total repository size even after you remove them from the current branch. To reduce the size of the repository, you must purge the files from its history.
Purging files rewrites the commit history of your repository. Anyone else working in the repository must pull the rewritten history afterwards, and any local work they have not pushed will be lost. Back up the repository before you start, and agree on the change with your team first.
To resolve this issue, ask your team’s internal Git experts to help you purge large files from your repository history. To identify which files are taking up the most space, you can ask Maia Team to locate large files for you, or export your branch as a .zip file and check the file sizes using your local operating system’s file manager or terminal tools. Once you have reduced the size of your repository, retry the Git action in Maia.
Only files that belong under version control should be committed to your repository. Data files, exports, archives, logs, and binaries belong in a filesystem or cloud storage instead. Because Git retains every version of a file, committing them even once increases your repository size permanently.To prevent this error from recurring, add any file types that do not belong in the repository to a .gitignore file so that they are not committed again.