What part of Azure DevOps stores your code?
Azure Repos holds the code and its Git history. Azure Boards tracks work items such as bugs. Azure Pipelines can run automated work. This profile uses hosted Azure DevOps Services. Azure DevOps Server is a separate self-managed offering.
Start with a private project you control. Keep a local copy and use the organization and project you intend to share with. A bug or task on a board is useful context for a code change. The task does not store the change itself.
How do you check a bug fix before it reaches the shared branch?
Create a pull request and link the work item. The reviewer can compare the actual lines with the bug report. An administrator can set a branch policy to require a review, build or linked work item before a merge.
Check the project’s actual permissions and policy. Microsoft documents permissions that can override a policy. Keep those privileges limited and use the ordinary review path for routine changes.
Who needs access and which parts of a move need separate work?
Microsoft’s hosted Basic plan lists the first five users free and includes unlimited private Git repositories. Check the access level for teammates who need code in a private project and account for automation or add-ons separately.
Save the Git history and check separately for large files, work items, review comments and branch policies. Microsoft’s Git import brings over Git LFS references but leaves the actual large files for a separate transfer. Verify a small sample at the destination before moving the working project.
How would you rehearse one review without using Azure DevOps?
Draw a fictional bug saying the settings button has the wrong label, and a proposed change in a separate branch. Use paper only.
- Connect the task to the proposed editWrite a pretend work item number and connect it to the branch review. The review should still show exactly which wording changes.
- Mark what blocks the mergeDraw the required reviewer and check. Mark the request as waiting until both are satisfied. Put any exceptional override outside this routine path.
- Plan the moveList the code history, the linked bug and one large image. Mark which belong in Git and which need separate verification at the destination.