Creating Repositories

What is a Repository?

A repository (or "repo") is a digital storage space where your source code and its entire history of changes are kept. It lets developers collaborate without stepping on each other’s toes, and ensures that every change is documented.

In Azure DevOps, you can use either:

• Git: A distributed version control system — modern, flexible, and used globally.
• TFVC (Team Foundation Version Control): A centralized version control system, often used in traditional enterprise setups.

Step-by-Step Guide to Creating a Repository

Creating a new repository is a great first step toward structured development. Here’s how to get started:

Step 1: Sign in to Azure DevOps

Head over to Azure DevOps and log in using your Microsoft account. Choose the organization and project where you want to create your repository.

Step 2: Navigate to Repos

On the left-hand side menu, click on Repos. This takes you to the source control section of your selected project. If your project doesn’t have a repo yet, you’ll see an option to create one.

Step 3: Create a New Repository

Click on "New Repository". You’ll be asked to enter the following details:

• Name: Choose a short, meaningful name for your repository (e.g., "weather-app" or "student-portal").
• Type: Select Git (recommended for most projects) or TFVC.

Once filled, click Create — and your repository is live!

Step 4: Clone the Repository

Now that your repo exists, it’s time to connect it to your local development environment.
If you're using Git, you can clone it by running this command in your terminal or Git Bash:

git clone <repository-url>

Replace <repository-url> with the link shown on the Azure Repos page. You can also use tools like Visual Studio, Visual Studio Code, or GitHub Desktop to clone the repo more visually.

Managing Your Repository

After creating your repository, you can take advantage of powerful DevOps features to manage it effectively:

• Branching: Create separate branches for features, bug fixes, or experiments without affecting the main code.
• Pull Requests: Collaborate and review code before merging changes — a great way to maintain code quality.
• Commit History: See every change ever made — who made it, when, and why.
• Permissions: Control who can read, write, or manage the repository through role-based access.

These features help teams stay organized, avoid conflicts, and ship reliable software together.

Tips for Beginners

• Start with Git: It’s beginner-friendly, powerful, and most widely used in the industry.
• Name your repos clearly: It helps when working with multiple projects or collaborators.
• Practice cloning and pushing: Try editing a README file, committing the change, and pushing it — you’ll get the hang of it fast.
• Don’t be afraid of branches: They’re your sandbox — you can experiment freely without breaking anything.

Conclusion

Repositories in Azure DevOps are more than just file storage — they’re a structured, collaborative workspace where your code is safe, tracked, and shared. Creating your first repo is an exciting milestone that unlocks the door to building and deploying real-world software.

Next up, we’ll explore how to clone, branch, and merge code — essential skills every developer needs when working with source control.