How to Move Repositories

If you need to move your Git repo between organizations, you will need to reconfigure FL0 so it can find the new repo.

Before moving a repository it's important to understand the impact on your FL0 workspace:

A FL0 workspace can be connected to multiple Github organization at a time
You cannot change the repository connected to a FL0 application, it must be deleted and recreated
Deleting and recreating a application will involve downtime unless you run both alongside each other with different names
While transferring the repository it will not be possible to push code changes to the application from the point the repo is moved to the point the FL0 application is reconnected
Allow 10 minutes per application to complete the migration. Duration can depend on the following factors:
1. Number of environment variables
2. Duration of build process
FL0 automatically generates unique URLs when you create a new application, which can be manually overridden. When migrating apps, make sure you update the new URL to match the old URL.

Transfer the repo to the new owner
In FL0, ensure you have a backup of all Development and Production environment variables
Delete the application in FL0
Create a new application in FL0, connecting it to the new repository location
Restore the environment variables
Run a new manual deployment to make the environment variables take effect
Update the URL to match the old URL

Transfer the repo to the new owner
In FL0, ensure you have a backup of all Development and Production environment variables
Create a new application in FL0 with a new name, connecting it to the new repository location
Copy the environment variables, adjusting any references to the application URL
Run a new manual deployment to make the environment variables take effect
Switch any external applications to use the new application URL such as websites, mobile apps, webhooks, etc.
Delete the old FL0 application once satisfied that no traffic is hitting it