When you create a workspace, you have the option of creating a scratch repository, instead of a new repository or using a clone of the project's Git repository. You may want to create a scratch repository 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, no build pipeline is set up to publish your changes to an environment. If you want to build and publish your artifacts, you may want to create a new repository and branch, instead of a scratch repository.

If you've created a scratch repository and now want to build and publish your artifacts, you'll need to first push the scratch repository to a new remote repository. When creating this new repository, you'll have the option of creating a CI/CD pipeline with jobs for packaging the build artifacts from the repository and deploying them to your environment. See Push Your Scratch Repository to the Remote Repository.