When using an Azure DevOps code repository, you need to first clone it to your local machine, as that is where you'll make your code changes and perform all your development tasks. Cloning will create a local copy of that repository and will download any files that currently exist at that time in that repository. You can create branches within your local repository to perform your development.
Once you have the repository cloned, you are free to do your coding and make all the changes you need to make. As you are making changes and testing, you can commit that code to your local repository as much as you want, but it will only exist on your local machine until you push it to Azure DevOps.
You can push your changes to Azure DevOps in a few different ways:
- Use the Synchronize Changes button to both push your changes up to Azure DevOps and to pull any changes down from Azure DevOps.
- Use the Push menu command in the Source Control menu.
- Use the Git push command in Terminal Window.
Making code changes in older versions of the repository will likely lead to merge conflicts that you will have to resolve when you push your changes up to DevOps.
Before beginning any development task, it's a good idea to make sure that your local repository is up to date.