Azure Repos Workshop
Agenda
• Azure Repos
• Files
• Commits
• Pushes
• Branches
• Tags
• Pull Requests
• Q&A
Azure Repos
• Git repository within Azure DevOps
• Alternative for other version control software
• GitHub
• TFS
• CVS
• SVN
• …
Creating a repository
• Multiple ways to create a repository
• Web
• CLI
• IDEs (VS, Xcode, IntelliJ, Eclipse)
• A repository generally contains code and documentation
• Existing repositories can be cloned
Files
• Displays your files and folders in the browser
• Displays any readme markup files
• You can see the history per file
Commits
• Shows all individual commits for the selected branch
• Filter branches on name and tags
• Filter commits on commit id, date, and author
Pushes
• Shows all pushes for the selected branch
• See the commits per push
• Filter pushes on name and tags
• Filter pushes on date and user
• There is an indication noting whether a triggered (pipeline) build was successful or not
Branches
• Shows mine, all, and stale branches
• Can filter on branch names
• Can create new branches
• See the status of a triggered pipeline
• See the pull request the branch is related to
• See how many commits this branch is ahead or behind of the compare branch
• Set up branch policies
Branch Policies
• In general, you will want to set up policies on important branches
• Automatically applied to pull requests into these branches
• Examples
• Minimum number of reviewers
• Checking for linked work items
• Checking for comment resolution
• Build validations
• Quality gate status checks
Tags
• Create additional tags
• Find commits by tag
Pull Requests
• Pull requests are organized by mine, active, completed, abandoned
• Filter by pull request id and user
• Pull requests can require passing various checks before allowing completion
• These checks can be enforced by branch policies
• Can be set to autocomplete once all checks pass
Pull Requests
• A description can be added to the pull requests and comments can be written
• All separate updates (commits and pushes) can be checked
• Files can be inspected in the pull request
• Conflicts may be resolved in the pull request
Azure DevOps Pull Requests
Q&A
• Time for questions