When you create a workspace, you have the option to create a scratch repository, rather than a new repository (which is based on the main branch of the project's repository). It's helpful 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. If you want to let your team members use your scratch repository, you'll need to push the scratch repository to a new remote repository so your teammates can clone it.

When you create a Git repository for your workspace, VB Studio automatically sets up packaging and build jobs and adds them to a CI/CD pipeline, allowing you to build and publish your artifacts simply by clicking Publish. If you opt for a scratch repository, however, these jobs are not initially set up for you, unless you decide you want to publish the changes in your scratch repo. To do this, you'll need to first push your changes to a remote repository, at which time VB Studio asks you to identify the target repository, then creates the required package and deploy jobs for you as part of a build pipeline. (You have the option to not create this pipeline, if that's what you want.) See Push a Scratch Repository to a Remote Repository for more information.