Azure Repos for source control - Step-by-Step Execution

Process Flow - Azure Repos for source control

Developer writes code

↓

Code added to local repo

↓

Commit changes locally

↓

Push commits to Azure Repos

↓

Azure Repos stores code securely

↓

Team members pull latest code

↓

Repeat cycle for updates

This flow shows how developers write code, commit locally, push to Azure Repos, and team members pull updates to collaborate.

Execution Sample

Azure

git add .
git commit -m "Add feature"
git push origin main

This sequence stages changes, commits them locally with a message, then pushes to Azure Repos main branch.

Process Table

Step	Action	Command	Result
1	Stage changes	git add .	All changes marked for commit
2	Commit changes	git commit -m "Add feature"	Changes saved locally with message
3	Push to Azure Repos	git push origin main	Changes uploaded to remote repo
4	Team pulls changes	git pull origin main	Local repo updated with latest code
5	End	-	Code synchronized across team

💡 Code is synchronized when team pulls latest changes from Azure Repos.

Status Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4
Local repo state	No changes staged	Changes staged	Changes committed locally	Changes pushed to remote	Local repo updated with remote

Key Moments - 2 Insights

Why do we need to commit changes before pushing?

Committing saves your changes locally as a snapshot. Without commit, there is nothing to push to Azure Repos. See execution_table step 2 and 3.

What happens if team members don’t pull latest changes?

They will work on outdated code, causing conflicts later. Pulling updates keeps everyone synchronized. See execution_table step 4.

Visual Quiz - 3 Questions

Look at the execution table, what command stages changes for commit?

A git push origin main

B git add .

C git commit -m "Add feature"

D git pull origin main

💡 Hint

Check Step 1 in the execution_table under Command column.

At which step are changes saved locally as a snapshot?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

Look at the Result column in Step 2 of execution_table.

If a developer skips 'git pull', what is the likely outcome?

A Code conflicts may occur later

B Changes are pushed twice

C Local repo updates automatically

D Code is deleted from Azure Repos

💡 Hint

Refer to key_moments about team synchronization and execution_table Step 4.

Concept Snapshot

Azure Repos stores your code remotely.
Use 'git add' to stage changes.
Use 'git commit' to save changes locally.
Use 'git push' to upload to Azure Repos.
Team members use 'git pull' to get updates.
This keeps code safe and shared.

Full Transcript

Azure Repos is a service to store and manage your code safely in the cloud. Developers write code on their computers and use commands to save and share it. First, they stage changes with 'git add', then save them locally with 'git commit'. After that, they upload the changes to Azure Repos using 'git push'. Other team members download the latest code with 'git pull' to stay updated. This cycle repeats as the team works together, ensuring everyone has the latest code version.

Practice

1. What is the main purpose of Azure Repos in software development?

easy

A. To design user interfaces

B. To store code safely and track changes over time

C. To run applications in the cloud

D. To manage virtual machines

Solution

1. Step 1: Understand Azure Repos role

   Azure Repos is a service that stores source code and tracks changes made by developers.

2. Step 2: Compare options with Azure Repos function

   Options A, B, and D describe other Azure services or tasks unrelated to source control.

3. Final Answer:

   To store code safely and track changes over time -> Option B

4. Quick Check:

   Azure Repos = Code storage and version tracking [OK]

Hint: Azure Repos is about code storage and history [OK]

Common Mistakes:

• Confusing Azure Repos with Azure App Services
• Thinking Azure Repos manages cloud infrastructure
• Mixing source control with deployment services

2. Which Git command is used to send your local code changes to Azure Repos?

easy

A. git pull

B. git clone

C. git push

D. git branch

Solution

1. Step 1: Identify command to send changes

   The git push command uploads local commits to the remote repository like Azure Repos.

2. Step 2: Understand other commands

   git clone copies a repo, git pull fetches and merges changes, git branch manages branches.

3. Final Answer:

   git push -> Option C

4. Quick Check:

   Send changes = git push [OK]

Hint: Push means send your changes to the server [OK]

Common Mistakes:

• Using git clone to send changes
• Confusing git pull with git push
• Thinking git branch sends code

3. Given this Git command sequence in Azure Repos:

git clone https://dev.azure.com/org/project/_git/repo
cd repo
git checkout -b feature1
git commit -m "Add feature"
git push -u origin feature1

What is the result?

medium

A. A new branch 'feature1' is created locally and pushed to Azure Repos

B. The main branch is overwritten with feature1 changes

C. The repository is deleted from Azure Repos

D. The commit message is ignored

Solution

1. Step 1: Analyze branch creation and commit

   git checkout -b feature1 creates and switches to a new branch named 'feature1'. The commit adds changes to this branch.

2. Step 2: Understand push command effect

   git push -u origin feature1 uploads the new branch and sets it to track the remote branch in Azure Repos.

3. Final Answer:

   A new branch 'feature1' is created locally and pushed to Azure Repos -> Option A

4. Quick Check:

   Branch created and pushed = A new branch 'feature1' is created locally and pushed to Azure Repos [OK]

Hint: Checkout -b creates branch; push uploads it [OK]

Common Mistakes:

• Assuming main branch is overwritten
• Thinking repository is deleted
• Ignoring the commit message effect

4. You try to push changes to Azure Repos but get an error about non-fast-forward updates. What should you do to fix this?

medium

A. Run git pull to update your local branch before pushing

B. Delete the remote repository and push again

C. Use git clone again to overwrite your local repo

D. Ignore the error and push with --force immediately

Solution

1. Step 1: Understand non-fast-forward error

   This error means the remote branch has changes your local branch lacks, so push is rejected to avoid overwriting.

2. Step 2: Fix by syncing local branch

   Running git pull fetches and merges remote changes into your local branch, resolving conflicts before push.

3. Final Answer:

   Run git pull to update your local branch before pushing -> Option A

4. Quick Check:

   Sync local branch first = git pull [OK]

Hint: Pull first to sync before pushing [OK]

Common Mistakes:

• Forcing push without syncing
• Deleting remote repo unnecessarily
• Cloning again instead of pulling

5. Your team uses Azure Repos and wants to protect the main branch from direct changes. Which feature should you enable to require pull requests for all changes?

hard

A. Create a new repository for each developer

B. Enable Git Large File Storage (LFS)

C. Set up Azure Pipelines for continuous deployment

D. Branch policies with pull request requirements

Solution

1. Step 1: Identify feature to protect main branch

   Branch policies in Azure Repos allow setting rules like requiring pull requests before merging to main.

2. Step 2: Evaluate other options

   Git LFS manages large files, pipelines automate deployment, and creating repos per developer doesn't protect main branch.

3. Final Answer:

   Branch policies with pull request requirements -> Option D

4. Quick Check:

   Protect main branch = branch policies [OK]

Hint: Use branch policies to require pull requests [OK]

Common Mistakes:

• Confusing deployment pipelines with branch protection
• Thinking Git LFS controls code changes
• Creating multiple repos instead of using policies