Push Your Scratch Repository to the Remote Repository
If you chose to use a scratch repository when creating your workspace, you'll need to push the scratch repository to the remote repository if you want other team members to see its contents. A remote repository is also required to fully use Git operations within the Designer. Pushing your scratch repository creates a new remote Git repository in the project.
When creating your new remote repository, you'll also have the option to create a CI/CD pipeline with jobs for packaging the build artifacts from the repository and deploying the artifacts to your environment.
For details on pushing a scratch repository to a remote repository, see:
- Push a Scratch Repository to a Git Repository if you're working with visual applications
- Push a Scratch Repository to a Git Repository if you're working with extensions