---
title: "Sync your RShift Sites project with Bitbucket"
description: "Export and two-way sync your RShift Sites project code with a Bitbucket Cloud workspace for code backup, collaboration, and deployment."
image: "https://help.rshift.com/og.svg"
---

> Documentation Index
> Fetch the complete documentation index at: https://help.rshift.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Sync your RShift Sites project with Bitbucket

&lt;head>
  &lt;script type="application/ld+json">
    &#123;`{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Do I need to know Bitbucket to use this feature?", "acceptedAnswer": {"@type": "Answer", "text": "No. Connect and authorize once, and Bitbucket safely stores your code. You only need to learn Bitbucket's features if you want to do more advanced things such as branching, pull requests, or Bitbucket Pipelines."}}, {"@type": "Question", "name": "Does RShift Sites support Bitbucket Data Center or Bitbucket Server?", "acceptedAnswer": {"@type": "Answer", "text": "No. RShift Sites syncs with Bitbucket Cloud (bitbucket.org) only and does not support self-hosted Bitbucket Data Center or Bitbucket Server instances."}}, {"@type": "Question", "name": "Is the repository RShift Sites creates public or private?", "acceptedAnswer": {"@type": "Answer", "text": "Repositories created by RShift Sites are private, on every plan. Nobody can see your code on Bitbucket unless you change the repository's access level yourself in Bitbucket."}}, {"@type": "Question", "name": "What happens if I rename my Bitbucket repository?", "acceptedAnswer": {"@type": "Answer", "text": "Sync continues. RShift Sites identifies your repository and Bitbucket workspace by their internal IDs, not by their names, so it follows repository renames automatically, even when Bitbucket does not deliver the rename notification. The repository link in your project settings updates to the new name."}}, {"@type": "Question", "name": "What happens if I rename my Bitbucket workspace?", "acceptedAnswer": {"@type": "Answer", "text": "Sync continues. RShift Sites identifies the workspace by its internal ID rather than its name, so changing the workspace ID or name in Bitbucket does not break the connection. The workspace name shown in RShift Sites updates the next time a workspace owner or admin reconnects the connection."}}, {"@type": "Question", "name": "What happens if I move my repository to another Bitbucket workspace?", "acceptedAnswer": {"@type": "Answer", "text": "If your RShift Sites workspace also has a connection to the destination Bitbucket workspace, sync follows the repository there. Otherwise RShift Sites disconnects the project. Add a connection to the destination workspace, then reconnect the project. When you reconnect, RShift Sites creates a new repository."}}, {"@type": "Question", "name": "What happens if I delete my Bitbucket repository?", "acceptedAnswer": {"@type": "Answer", "text": "The connection breaks and the project stops syncing. Your project and its code stay in RShift Sites. Disconnect the project and connect it again to create a new repository with your current code."}}, {"@type": "Question", "name": "How can I switch to a different Bitbucket workspace or Atlassian account?", "acceptedAnswer": {"@type": "Answer", "text": "You can't change the linked workspace on an existing project. Disconnect the project from Bitbucket, add a connection for the other workspace if you don't have one yet, and connect the project to that connection. RShift Sites creates a new repository. The original repository stays on Bitbucket but is no longer linked to RShift Sites."}}, {"@type": "Question", "name": "Can I disconnect from Bitbucket?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. Workspace or project admins and owners can disconnect a project from Bitbucket at any time in the project's Bitbucket settings. Your repository stays on Bitbucket, but syncing stops. If you reconnect later, RShift Sites creates a new repository."}}, {"@type": "Question", "name": "Can I import an existing Bitbucket repository into RShift Sites?", "acceptedAnswer": {"@type": "Answer", "text": "No. You can only export from RShift Sites to Bitbucket, not the other way around. When you connect a project, RShift Sites always creates a new repository."}}, {"@type": "Question", "name": "Can I connect multiple Bitbucket workspaces?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. A RShift Sites workspace can have a connection to each Bitbucket workspace you have admin access to. Each Bitbucket workspace can be connected once per RShift Sites workspace. Each RShift Sites project is then linked to one repository in one of those workspaces."}}, {"@type": "Question", "name": "Who is the author of commits RShift Sites makes on Bitbucket?", "acceptedAnswer": {"@type": "Answer", "text": "Commits made by RShift Sites are authored by RShift Sites' bot identity. In the commit log the author reads gpt-engineer-app[bot], an earlier name for that identity, and Bitbucket does not link it to an account. RShift Sites makes the pushes through the authorization of the Atlassian account that connected the workspace."}}]}`&#125;
  &lt;/script>
&lt;/head>

When you build with RShift Sites, your project code is stored and managed inside the RShift Sites platform.

[Bitbucket](https://bitbucket.org/) is Atlassian's platform for storing, managing, and sharing code, with version control, pull requests and code reviews, Bitbucket Pipelines for automated builds and deployments, and Jira integration.

If you want your own copy, plan to collaborate with developers, or move your project elsewhere, you can export and sync your project to Bitbucket Cloud: back up your code, review changes in pull requests, work locally in your IDE, test features on branches, and deploy outside RShift Sites.

For the full picture of what Git sync is, how the two-way sync model works across providers, and how to choose between GitHub, GitLab, and Bitbucket, see the [Git sync overview](/sites/integrations/git-sync-overview/).

> **Note**
>
> RShift Sites syncs with **Bitbucket Cloud** (bitbucket.org). RShift Sites does not support self-hosted **Bitbucket Data Center** or **Bitbucket Server** instances.

> **Note**
>
> You don't need Bitbucket to use RShift Sites. Many users build and launch entirely within RShift Sites. If you only need a copy of your code, you can download your code directly from RShift Sites: use the **Download codebase** section in **Project settings → Git**, or open the [Code editor](/sites/features/code-mode/) and click **Download codebase** at the bottom of the file tree sidebar (paid plans).

## How Bitbucket Git sync works

Like all [Git sync](/sites/integrations/git-sync-overview/), the Bitbucket integration has two layers:

1. A **workspace connection**
2. A **project repository link**

### Workspace connection

A workspace connection authorizes RShift Sites to access one Bitbucket Cloud workspace. You sign in with your Atlassian account and grant RShift Sites access, then choose the Bitbucket workspace to connect. RShift Sites registers a webhook on that workspace so that changes on Bitbucket reach your projects. A webhook is a notification Bitbucket sends to RShift Sites whenever something happens in the workspace, such as a push.

Every project in the RShift Sites workspace can use the same workspace connection.

A RShift Sites workspace can contain:

* Multiple Bitbucket connections, one per Bitbucket workspace
* Bitbucket connections alongside GitHub and GitLab connections

Each Bitbucket workspace can be connected once per RShift Sites workspace.

> **Note**
>
> You need **admin** access to the Bitbucket workspace you connect. RShift Sites registers a workspace-level webhook during setup, and Bitbucket only allows workspace admins to do that.

### Project repository link

A project repository link connects one RShift Sites project to one Bitbucket repository.

When connected:

* Changes made in RShift Sites sync to Bitbucket
* Changes pushed to the active Bitbucket branch sync back into RShift Sites
* RShift Sites only edits and syncs one branch at a time

### Role-based access for Bitbucket integration

| Role                                                                          | Allowed action                                                                                                                                                                                                                                                                                                        |
| ----------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Workspace owner or admin only                                                 | <ul><li>Add a workspace connection</li><li>Reconnect a workspace connection (re-authorize with Atlassian)</li><li>Unlink projects from a workspace connection</li><li>Delete a workspace connection</li><li>Enable or disable **Include member email addresses in commits** (Business and Enterprise plans)</li></ul> |
| <ul><li>Workspace owner or admin</li><li>Project owner or admin</li></ul>     | <ul><li>Connect a project to a repository</li><li>Disconnect a project from a repository</li></ul>                                                                                                                                                                                                                    |
| <ul><li>Workspace editor or higher</li><li>Project editor or higher</li></ul> | <ul><li>View sync status</li><li>Switch branches</li><li>Create branches</li><li>View the connection in Workspace settings → Git → Bitbucket</li></ul>                                                                                                                                                                |

## Create a workspace Bitbucket connection

**Workspace admins and owners** can create workspace connections from:

* [**Workspace settings → Git**](https://lovable.dev/settings/git) **→ Bitbucket → Add connection**
* [**Project settings → Git**](/sites/features/projects/settings/#git-tab) **→ Bitbucket → Add connection** (if a project has not been connected yet)

You need an Atlassian account with admin access to at least one Bitbucket Cloud workspace. You can create a Bitbucket account for free at [bitbucket.org](https://bitbucket.org/).

**Add a new connection**

Click **Add connection**. The **Connect Bitbucket** screen opens.

**Authorize with Bitbucket**

Click **Authorize with Bitbucket**. A popup opens to Atlassian's sign-in page. Sign in and grant RShift Sites access.

    Atlassian stores the authorization on your Atlassian account, not on the Bitbucket workspace. You can review or revoke it later under **Connected apps** in your Atlassian account settings.

**Select a workspace**

Under **Select workspace**, RShift Sites lists the Bitbucket workspaces available on your account. Click **Connect** next to the workspace you want to use.

    If only one workspace is available, RShift Sites connects it directly and skips this step. Workspaces that are already connected to your RShift Sites workspace do not appear in the list.

> **Danger**
>
> A Bitbucket workspace you created within the last few minutes cannot receive pushes yet, because Bitbucket activates new workspaces with a short delay. If you connect a project right after creating the workspace, RShift Sites shows how long to wait. Try again after that time.

## Link a project to a Bitbucket repository

With an active workspace Bitbucket connection in place, **workspace or project admins and owners** can connect a RShift Sites project to a Bitbucket repository.

* When you connect a project, RShift Sites creates a new Bitbucket repository. The repository is **private**, so nobody can see your code unless you change its access level on Bitbucket.
* The repository is named after your project. If the workspace already has an empty repository with that name, RShift Sites uses it. If the existing repository has commits, RShift Sites adds a short suffix to the new repository's name instead.
* Each RShift Sites project can connect to one repository on one provider. If the project already syncs with GitHub or GitLab, the Bitbucket card does not appear in **Project settings → Git** until you [disconnect the project](/sites/integrations/git-sync-overview/#disconnecting-and-reconnecting) from that provider.

**Open the project's Bitbucket settings**

Open **Project settings → Git → Bitbucket**.

**Connect the project**

Under **Connect project**, click **Connect** next to the Bitbucket workspace where the new repository should be created.

    RShift Sites creates a new Bitbucket repository and starts two-way sync automatically.

> **Danger**
>
> Don't delete your Bitbucket repository or move it to a Bitbucket workspace that is not connected to your RShift Sites workspace. Doing so breaks the sync, and RShift Sites won't be able to update your project. You can rename the repository or the Bitbucket workspace: RShift Sites tracks both automatically.

## Manage a project's repository sync

After connecting a project to a Bitbucket repository, you see the following in the project's Bitbucket settings:

* Repository status as **Connected**
* [Sync status](/sites/integrations/git-sync-overview/#sync-status) card showing whether RShift Sites and Bitbucket are on the same commit
* Branch picker with active branch name (Bitbucket branch synced with RShift Sites)
* Clone URLs (HTTPS, SSH)
* Option to **View on Bitbucket** (available from the dropdown)
* Option to **Disconnect** (available from the dropdown)

RShift Sites only edits and syncs one branch at a time. By default, this is the `main` branch. Changes pushed to the currently active branch sync back into RShift Sites.

If the sync status card says **RShift Sites and Bitbucket have diverged**, RShift Sites and Bitbucket each have commits that the other does not. RShift Sites pushes its changes to the `lovable-sync` branch instead of the synced branch, as described under [Troubleshooting](#troubleshooting), and the next sync from Bitbucket replaces RShift Sites' version of the branch with the Bitbucket version. **Re-check** compares the branches again and doesn't sync anything.

### Switch branches

Use the branch picker in the project's Bitbucket settings to change which branch RShift Sites edits and syncs.

1. Click the branch picker.
2. Search or select a branch.
3. Click the branch to switch.

RShift Sites immediately starts editing and syncing the branch you switched to.

You can switch back to the default branch at any time.

### Create a new branch

You can create a branch from the same picker without leaving RShift Sites.

1. Click the branch picker.
2. Click **Create branch** at the bottom of the list.
3. Enter a branch name. RShift Sites validates it against empty names, invalid characters, and duplicates.

> **Note**
>
> Branch names must follow Git naming rules (no spaces, .., leading or trailing dots or dashes, and special characters such as \~ ^ : ? \* \[ ] \\).

RShift Sites creates the new branch from the **currently active branch** as its source (shown as `Source: <active branch>` in the dialog). RShift Sites automatically switches to the new branch and starts editing and syncing it.

> **Danger**
>
> The source is your **currently active branch**, not the repository's default branch. If you want to start a new feature branch from `main`, switch to `main` first, then create the new branch.

> **Note**
>
> You can't switch branches or create new branches while RShift Sites is editing the project.

### Clone the repository locally

After connecting a project, RShift Sites provides clone URLs for:

* HTTPS
* SSH

You can clone the repository locally and continue working in your preferred IDE.

### Commit attribution

Commits made by RShift Sites are authored by RShift Sites' bot identity. In the commit log the author reads `gpt-engineer-app[bot]`, an earlier name for that identity, and Bitbucket does not link it to an account. RShift Sites pushes the commits through the authorization of the Atlassian account that connected the workspace. That account is not necessarily the member who made the change, and RShift Sites does not add a `Co-authored-by` line on Bitbucket repositories.

To record who triggered each commit, enable **Include member email addresses in commits** in workspace settings. See [Commit attribution](/sites/integrations/git-sync-overview/#commit-attribution) (Business and Enterprise plans).

### Disconnect a project from Bitbucket

When you disconnect a project, RShift Sites removes the link between the project and its Bitbucket repository.

When you disconnect:

* **Sync stops.** The two-way connection between RShift Sites and Bitbucket ends.
* **Your repository stays on Bitbucket.** It remains intact with all history and files.
* **Your project and its code stay in RShift Sites.** Future changes are stored only inside RShift Sites.

RShift Sites keeps the workspace connection when you disconnect a project.

**Workspace or project admins and owners** can disconnect from the project's Bitbucket settings: in the active repository connection, open the dropdown, select **Disconnect**, type the repository name to confirm, and click **Disconnect**.

If a project needs Bitbucket again, you can link it to any available connection. If you reconnect later:

* RShift Sites creates a new repository with the current version of your project.
* The original repository stays unchanged on Bitbucket and is no longer linked to RShift Sites.

## Unlink projects from a workspace Bitbucket connection

**Workspace admins and owners** can remove specific projects from a connection without deleting the connection entirely. The connection remains available for other projects.

**Open Bitbucket settings**

Open **Workspace settings → Git → Bitbucket**.

**Open the connection**

Open the connection you want to manage.

**Select projects**

Under **Linked projects**, check the projects you want to unlink.

**Confirm**

* Click **Unlink N projects** (where `N` is the number of projects you selected)
    * Click **Unlink** to confirm

When unlinked, those projects no longer sync through this connection.

## Delete a workspace Bitbucket connection

**Workspace admins and owners** can delete Bitbucket connections.

When you delete a workspace Bitbucket connection, RShift Sites:

* Removes the connection for all projects
* Stops syncing for linked projects
* Removes the RShift Sites webhook from the Bitbucket workspace
* Keeps the repositories on Bitbucket
* Deletes the stored credentials

> **Danger**
>
> You cannot restore a deleted connection. Projects that used it stop syncing until a workspace admin or owner adds a new connection and reconnects each project.

**Open Bitbucket settings**

Open **Workspace settings → Git → Bitbucket**.

**Open the connection you want to remove**

Select the connection from the list.

**Review linked projects**

Review the **Linked projects** section carefully before deleting the connection to avoid unintentionally removing Bitbucket sync.

**Delete**

Under **Delete this connection**, click **Delete**, type the connection name to confirm, and click **Delete**.

## Limitations

The Bitbucket Git sync integration currently does not support:

* Bitbucket Data Center or Bitbucket Server. RShift Sites supports Bitbucket Cloud (bitbucket.org) only.
* Importing existing Bitbucket repositories into RShift Sites. You can only export from RShift Sites to Bitbucket.
* Reconnecting to the same repository after disconnecting. RShift Sites creates a new repository on reconnect.
* Connecting the same Bitbucket workspace more than once.
* Following a repository moved to a Bitbucket workspace that is not connected to your RShift Sites workspace.

## FAQ

**Do I need to know Bitbucket to use this feature?**

No. Connect and authorize once, and Bitbucket safely stores your code.

    You only need to learn Bitbucket's features if you want to do more advanced things such as branching, pull requests, or Bitbucket Pipelines.

**Does RShift Sites support Bitbucket Data Center or Bitbucket Server?**

No. RShift Sites syncs with Bitbucket Cloud (bitbucket.org) only and does not support self-hosted Bitbucket Data Center or Bitbucket Server instances.

**Is the repository RShift Sites creates public or private?**

Repositories created by RShift Sites are **private**, on every plan. Nobody can see your code on Bitbucket unless you change the repository's access level yourself in Bitbucket.

**What happens if I rename my Bitbucket repository?**

Sync continues. RShift Sites identifies your repository and Bitbucket workspace by their internal IDs, not by their names, so it follows repository renames automatically, even when Bitbucket does not deliver the rename notification. The repository link in your project settings updates to the new name.

**What happens if I rename my Bitbucket workspace?**

Sync continues. RShift Sites identifies the workspace by its internal ID rather than its name, so changing the workspace ID or name in Bitbucket does not break the connection. The workspace name shown in RShift Sites updates the next time a workspace owner or admin reconnects the connection.

**What happens if I move my repository to another Bitbucket workspace?**

If your RShift Sites workspace also has a connection to the destination Bitbucket workspace, sync follows the repository there.

    Otherwise RShift Sites disconnects the project. To resume syncing:

    1. Add a workspace connection for the destination Bitbucket workspace.
    2. Open the project's Bitbucket settings and connect the project to that connection.

    When you reconnect, RShift Sites creates a new repository. The moved repository stays on Bitbucket but is no longer linked to RShift Sites.

**What happens if I delete my Bitbucket repository?**

The connection breaks and the project stops syncing. Your project and its code stay in RShift Sites. Disconnect the project and connect it again to create a new repository with your current code.

**How can I switch to a different Bitbucket workspace or Atlassian account?**

You can't change the linked workspace on an existing project. As a workaround:

    1. Disconnect the project from Bitbucket in the project's Bitbucket settings.
    2. Add a connection for the other Bitbucket workspace, if your RShift Sites workspace doesn't have one yet.
    3. Connect the project to that connection.

    RShift Sites creates a new repository. The original repository stays on Bitbucket but is no longer linked to RShift Sites.

**Can I disconnect from Bitbucket?**

Yes. Workspace or project admins and owners can [disconnect a project from Bitbucket](#disconnect-a-project-from-bitbucket) at any time in the project's Bitbucket settings. Your repository stays on Bitbucket, but syncing stops. If you reconnect later, RShift Sites creates a new repository.

**Can I import an existing Bitbucket repository into RShift Sites?**

No. You can only export from RShift Sites to Bitbucket, not the other way around. When you connect a project, RShift Sites always creates a new repository.

**Can I connect multiple Bitbucket workspaces?**

Yes. A RShift Sites workspace can have a connection to each Bitbucket workspace you have admin access to. Each Bitbucket workspace can be connected once per RShift Sites workspace. Each RShift Sites project is then linked to one repository in one of those workspaces.

**Who is the author of commits RShift Sites makes on Bitbucket?**

Commits made by RShift Sites are authored by RShift Sites' bot identity. In the commit log the author reads `gpt-engineer-app[bot]`, an earlier name for that identity, and Bitbucket does not link it to an account. RShift Sites makes the pushes through the authorization of the Atlassian account that connected the workspace.

## Troubleshooting

When something goes wrong, RShift Sites shows a **Connection lost** message with a **Reconnect** button in the affected project's Bitbucket settings.

**Clicking 'Authorize with Bitbucket' does nothing, or shows a blocked sign-in window message.**

Your browser blocked the Bitbucket sign-in popup. Allow popups for RShift Sites and try again.

**The connected git provider session has expired or been revoked. Reconnect to continue syncing.**

RShift Sites lost access to your Bitbucket workspace, most often because someone removed RShift Sites under **Connected apps** in their Atlassian account, or because the Atlassian account that connected the workspace lost access to it.

    A workspace owner or admin can restore it:

    1. Open the affected project's Bitbucket settings.
    2. Click **Reconnect**. A popup opens to Atlassian's sign-in page.
    3. Sign in with an account that has admin access to the same Bitbucket workspace and grant RShift Sites access.

    Sync resumes for every project on this connection. Commits pushed to Bitbucket while access was revoked appear in RShift Sites after the next push to the synced branch.

    A workspace owner or admin can also reconnect from the connection itself: open **Workspace settings → Git → Bitbucket**, select the connection, and click **Reconnect**. Use this path for a connection that has no linked project.

**The RShift Sites webhook on this Bitbucket workspace was removed, so changes made in Bitbucket no longer reach this project. Reconnect to restore it.**

A Bitbucket workspace admin deleted the **RShift Sites GitSync** webhook in the workspace's webhook settings. Edits made in RShift Sites still reach Bitbucket, but pushes to Bitbucket no longer reach RShift Sites.

    Open the project's Bitbucket settings and click **Reconnect**. RShift Sites registers the webhook again.

**New Bitbucket workspaces take a few minutes to activate; retry shortly.**

Bitbucket rejects pushes to a workspace for several minutes after the workspace is created, and Bitbucket shows the same message when a workspace exceeds its user limit or has a billing problem.

    If you created the workspace within the last few minutes, wait for the time shown in the message and connect the project again. If the message persists, check the workspace's user limit and billing in Bitbucket.

**This repository is no longer accessible. Try reconnecting, or disconnect to connect this project to a different repository.**

Someone deleted the repository on Bitbucket, or moved it to a Bitbucket workspace this RShift Sites workspace has no connection for.

    You can either:

    * **Restore the repository on Bitbucket.** Move it back to its original workspace. Sync resumes automatically.
    * **Start a new repository.** Open the project's Bitbucket settings, disconnect the project, then connect it again. RShift Sites creates a new Bitbucket repository with your current code.

**My commits and pushes from Bitbucket aren't showing up in RShift Sites.**

RShift Sites only syncs **one branch at a time**, and that is the branch the project is currently set to in its Bitbucket repository connection settings. By default this is `main`.

    If you pushed commits to a different branch in Bitbucket, you have two options:

    * **Merge your changes into the synced branch**. For example, open a pull request from your feature branch into `main` and merge it. RShift Sites then picks up those commits.
    * **Switch the synced branch in RShift Sites**. In your project's Bitbucket settings, select the branch where your commits live. RShift Sites starts editing and syncing that branch instead, and your commits will appear.

**I pushed to the synced branch, but the commits don't appear in RShift Sites and the sync status says Bitbucket is ahead.**

RShift Sites pulls your changes when Bitbucket notifies it about a push to the synced branch. If that notification never arrives, the commits from that push don't appear in RShift Sites, and RShift Sites doesn't pull them later without a new notification. The [sync status](/sites/integrations/git-sync-overview/#sync-status) card in the project's Bitbucket settings shows **Bitbucket is N commits ahead of RShift Sites** until the next sync.

    If the project shows the message that the RShift Sites webhook was removed, click **Reconnect** first. RShift Sites registers the webhook again. Without the webhook, a new push never notifies RShift Sites.

    In every other case **Reconnect** doesn't fix this. It appears only when the connection itself has a problem, and it restores access to the repository without pulling commits. **Re-check** on the sync status card compares the branches again and doesn't sync anything either.

    To make RShift Sites pull the missing commits, push a new commit to the synced branch. Any push works, including an empty commit:

```bash
git commit --allow-empty -m "Trigger RShift Sites sync"
git push
```

    RShift Sites then syncs the branch to its current state on Bitbucket, which includes the earlier commits.

    Before you push, confirm the branch and the state of your RShift Sites edits:

    * You're pushing to the repository and branch shown in [**Project settings → Git**](/sites/features/projects/settings/#git-tab) **→ Bitbucket**. Commits on other branches don't sync.
    * Your latest RShift Sites edits are already in the repository on Bitbucket. If the sync status says **RShift Sites and Bitbucket have diverged**, the push replaces RShift Sites' version of the branch with the Bitbucket version, and the project no longer contains edits made only in RShift Sites. Contact [RShift Sites Support](https://lovable.dev/support) before you push if you need those edits.

    If the commits still don't appear after a new push, contact [RShift Sites Support](https://lovable.dev/support).

**I see a &#x22;lovable-fallback&#x22; branch in the branch picker.**

Someone deleted the synced branch on Bitbucket. RShift Sites automatically switched the project to a new branch called `lovable-fallback` so that you can continue editing. Your repository is otherwise unchanged.

    Pick another branch or recreate the original branch. After you switch away, you can leave or delete `lovable-fallback` in Bitbucket.

**My push from RShift Sites ended up on a &#x22;lovable-sync&#x22; branch instead of the synced branch.**

Bitbucket rejected the push to your synced branch, most often because someone pushed a conflicting change that RShift Sites could not apply your work on top of. To avoid losing your work, RShift Sites pushed it to a branch named `lovable-sync` instead, and your project's Bitbucket settings show "Your changes conflict with commits on `<your branch>` and could not be merged automatically. They were pushed to the branch `lovable-sync` instead. Merge that branch into `<your branch>` to apply them."

    Open that branch on Bitbucket, review the changes, and merge them into your synced branch through your usual review process.

    When a later push is rejected too, RShift Sites adds those changes to the same `lovable-sync` branch. If you've added your own commits to `lovable-sync`, RShift Sites leaves them untouched and pushes to a new branch named `lovable-sync-<timestamp>` instead. Review and merge that branch the same way.

**RShift Sites can't edit a large file in my project.**

RShift Sites cannot save files larger than **10 MB** into your project. Files you push from your own computer can be larger (up to Bitbucket's own limits) and sync into RShift Sites, but any RShift Sites edit that touches a file over 10 MB fails. For large media, ask RShift Sites to "Migrate large files to CDN assets". See the [chat page FAQ](/sites/features/projects/chat/) for details.

## Related topics

- [Sync your RShift Sites project code with GitHub, GitLab, or Bitbucket](/sites/integrations/git-sync-overview/)
- [Sync your RShift Sites project with GitLab](/sites/integrations/gitlab/)
- [Sync your RShift Sites project with GitHub](/sites/integrations/github/)
- [Project settings](/sites/features/projects/settings/)

Source: https://help.rshift.com/sites/integrations/bitbucket/index.mdx