Learn how to use Projects in Replit Teams for collaborative development, version control, and managing multiple Replit Apps with git-based workflows.
Projects are currently a beta feature available to Teams. A Project is a set of connected, Replit Apps for better collaborative development and versioning. Within a Project, you can:
Projects leverage a technology called git to manage version control, but you don’t need to know anything about git to use Projects!
Projects are a great option:
Every Project is organized around having a main Replit App that is the source of truth. In this example Project, “AnvilWebServer” is the main Replit App. Each team member has their own fork where they can work, e.g. “MadisonFitch-07-03” is a fork off of the main Replit App.
The best practice for working within a Project is to:
To get started, fork any Replit App in your organization and you’ll be prompted to turn it into a Project:
If you choose the “Fork & start a Project” option, the Replit App you are in will become your main Replit App for the Project and you will be moved to a new fork where you can work on a feature.
When you open the fork in the workspace, you’ll see a Project tool open which informs you that you have no changes from the main Replit App yet:
If you were to make some changes, you would see them previewed in the Project tool. You can create a basic express server and see the changes:
You can run your Replit App and test your changes. When you are ready, you can click the “Merge changes…” button, and your changes will be pulled into the main Replit App. In the main AnvilWebServer Replit App, you would be able to now see the express server changes, and you can run the Replit App to see the server in action:
git
In the previous section, the “Merge changes…” button did some magic by executing a few git commands. You don’t need to know anything about git to use Projects, but if you are familiar with git, you can take more control over how changes are made in a Project.
If you modify you fork again to add a joke endpoint, you’ll see changes in the Project tool:
Instead of hitting “Merge,” you can use the git tool (or use the git
command in the shell) to commit specific changes when merging:
If you switch back to the Projects tool, you will see “Committed” changes and now can click the “Merge” button to pull only your committed changes into the main Replit App.
When in the workspace, the header bar will provide some extra navigation options and controls:
You can visit the Project’s dashboard from the sidebar, or via the workspace header link. You’ll see: