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

# FAQ & troubleshooting

> Common questions and solutions for cubic

This page addresses frequently asked questions and common obstacles you might encounter when using **cubic**.

## Can one large PR use all my review quota?

No. If an automatic review would use a significant portion of your monthly review quota, **cubic** asks for confirmation before starting it. Comment `@cubic-dev-ai review this` on the PR, or use a manual rerun, when you want **cubic** to review a large PR anyway.

Generated files, ignored paths, images, and other files that **cubic** would not review do not count toward this large-PR check.

## Why is my branch out of sync?

* **Symptoms**:
  * You see a message like "This branch is X commits behind `main`."
  * Merge conflicts pop up unexpectedly when creating or pushing a PR.
* **Cause**: Your local branch might be outdated compared to `main` or your parent branch.
* **Solution**:
  1. Pull the latest changes from remote:
     ```bash theme={null}
     git fetch origin main
     ```
  2. Run [`mg sync`](/reference/mg-sync) to rebase or merge your current branch onto the latest commits.

## I can't push my stack – conflict with remote?

* **Symptoms**:
  * `mg push` fails with a conflict error message.
  * GitHub shows a "resolve conflicts" prompt.
* **Cause**: One of your parent branches was rebased or force-pushed, and your local changes no longer match.
* **Solution**:
  1. Run `git fetch origin` to ensure you have the latest changes.
  2. Resolve conflicts locally, then commit.
  3. Retry `mg push`.\
     If the problem persists, confirm nobody has force-pushed `main`.

## Error codes or known tricky scenarios

* **`E-101: No .cubic directory found`**
  * Ensure you've run [`mg init`](/reference/mg-init) in your repo.
* **`E-202: Branch not tracked`**
  * Adopt the branch with [`mg adopt <branch_name>`](/reference/mg-adopt) or create a new one using [`mg branch`](/reference/mg-branch).
* **`E-303: Force push required`**
  * This appears if you rewrite commits on a published branch. You can force push, but coordinate with teammates to avoid confusion.
* **`E-404: Branch does not exist`**
  * Verify the branch name and ensure it's spelled correctly.
* **`E-409: Merge conflict`**
  * Resolve conflicts, `git add` the files, then continue your `mg sync` or `mg push` workflow.

## General tips

* **Keep Branches Small**: Smaller changes reduce merge conflicts and simplify troubleshooting.
* **Sync Frequently**: If you're constantly out of date, [handle updates & sync](/how-to-guides/handle-updates-sync) more often.
* **Check `mg list`**: If a branch is missing or incorrectly parented, reparent or adopt as needed.