Use a Scratch Repository

When you create a workspace, you have the option of creating a scratch repository, instead of a new repository based on the main branch of the project's repository. A scratch repository is useful when you're experimenting and you're pretty sure you'll never want to merge your changes into an existing repository.

A scratch repository is a private repository that only exists in your workspace. Only you can use the scratch repository, and it's deleted when you delete the workspace. While this option is good for exploring ideas and trying out things, keep in mind that you won't be able to perform advanced Git operations (such as switching branches, and pulling or merging changes) from within the Designer. Also, package and deploy jobs in a CI/CD pipeline—which allow you to build and publish your artifacts simply by clicking Publish in the Designer—won't be created for you.

If you want to leverage full Git functionality within the Designer and enable collaboration, you'll need to push the scratch repository to a new remote repository. This way, your teammates can clone the repository and build on your changes. Further, when you push your scratch repo to a remote repo, package and deploy jobs are automatically created for you as part of a build pipeline (you can choose to not create this pipeline, if that's what you want). See Push a Scratch Repository to a Remote Repository.