Utilize common version control operations with Git

📘Cisco DevNet Associate (200-901 DEVASC)

---

For the DEVASC exam, you must understand how Git works in a development environment. One of the most important Git operations is git clone. This command is used to copy an existing repository.

This topic is very important because developers and DevOps engineers frequently clone repositories to work on source code, automation scripts, APIs, infrastructure files, and CI/CD configurations.

---

1. What is Git?

Git is a distributed version control system.

It is used to:

• Track changes in source code
• Collaborate with multiple developers
• Manage different versions of applications
• Maintain history of changes

Git allows every developer to have a full copy of the repository on their local machine.

---

2. What is a Repository?

A repository (repo) is a storage location for:

• Source code
• Configuration files
• Documentation
• Automation scripts
• Infrastructure-as-Code files
• API definitions

A repository contains:

• Project files
• Commit history
• Branch information

Repositories can exist:

• Locally (on your computer)
• Remotely (on a Git server)

Common Git hosting platforms include:

• GitHub
• GitLab
• Bitbucket

---

3. What Does git clone Do?

The git clone command:

• Creates a copy of a remote repository
• Downloads all project files
• Downloads full commit history
• Sets up a connection to the original remote repository
• Creates a local working directory

In simple terms:

git clone = Download + Connect + Prepare to Work

---

4. Basic Syntax of git clone

git clone <repository-URL>

Example:

git clone https://github.com/example/project.git

After running this command:

• A new folder named project is created
• The full repository is copied inside it
• Git automatically configures a remote named origin

---

5. What Happens Internally During Clone?

When you run git clone, Git performs:

1. Creates a new directory
2. Initializes a new local Git repository
3. Downloads all objects (commits, trees, blobs)
4. Sets up the default remote (origin)
5. Checks out the default branch (usually main or master)

This means after cloning:

• You can immediately start working
• You have the entire history
• You are connected to the remote repository

---

6. Clone vs Download ZIP (Important for Exam)

Many beginners confuse cloning with downloading a ZIP file.

Download ZIP:

• Only downloads current files
• No commit history
• Not connected to repository
• Cannot push changes back

git clone:

• Downloads full commit history
• Maintains version tracking
• Allows pull and push
• Supports branching and merging

For DevOps and API development, cloning is required.

---

7. Clone Using HTTPS vs SSH

There are two common ways to clone:

1️⃣ HTTPS

git clone https://github.com/user/repo.git

• Uses username/password or token
• Easy to start with
• Common in enterprise environments

2️⃣ SSH

git clone git@github.com:user/repo.git

• Uses SSH key authentication
• More secure
• No need to enter password repeatedly
• Preferred for automation and CI/CD pipelines

For the DEVASC exam, know:

• HTTPS and SSH are both supported
• SSH requires key configuration

---

8. Cloning a Specific Branch

By default, Git clones the default branch.

To clone a specific branch:

git clone -b branch-name <repository-URL>

Example:

git clone -b develop https://github.com/user/project.git

This:

• Clones repository
• Checks out the specified branch immediately

---

9. Cloning Into a Custom Directory

You can specify a folder name:

git clone <repository-URL> custom-folder-name

Example:

git clone https://github.com/user/api-project.git api-dev

This creates a directory named api-dev.

---

10. Bare Clone (Advanced Concept)

git clone --bare <repository-URL>

A bare repository:

• Does NOT contain working files
• Only contains Git data
• Used for central repositories or servers

Used in:

• Git servers
• CI/CD infrastructure
• Central integration repositories

---

11. Shallow Clone (Performance Optimization)

Sometimes repositories are very large.

To clone only the latest commits:

git clone --depth 1 <repository-URL>

This:

• Downloads limited commit history
• Saves bandwidth
• Faster cloning

Used in:

• CI/CD pipelines
• Temporary build environments

---

12. Remote Configuration After Clone

After cloning, you can check remote configuration:

git remote -v

Output shows:

origin  https://github.com/user/repo.git (fetch)
origin  https://github.com/user/repo.git (push)

Important exam point:

• Default remote name = origin
• You can rename or change it

---

13. Common IT Use Cases of git clone

In real IT environments:

API Development

Developers clone API repositories to:

• Modify endpoints
• Update Swagger/OpenAPI definitions
• Add authentication logic

Network Automation

Engineers clone repositories containing:

• Python automation scripts
• Ansible playbooks
• Infrastructure configuration files

DevOps Pipelines

CI/CD systems:

• Clone repository
• Build application
• Run tests
• Deploy to server

Infrastructure as Code

Engineers clone repositories that contain:

• Terraform files
• Kubernetes YAML files
• CloudFormation templates

---

14. Authentication Considerations

When cloning private repositories:

• HTTPS requires Personal Access Token
• SSH requires configured SSH key
• Enterprise Git servers may use SSO

For the exam:

• Understand authentication methods
• Know difference between public and private repositories

---

15. Common Errors During Clone

You may see:

1. Authentication failed

Cause:

• Wrong credentials
• Expired token

2. Repository not found

Cause:

• Incorrect URL
• No access permission

3. Permission denied (SSH)

Cause:

• SSH key not configured
• SSH key not added to Git server

---

16. Clone vs Fork (Important Difference)

Cloning:

• Creates a local copy

Forking:

• Creates a copy under your account on Git platform

Workflow:

1. Fork repository on GitHub
2. Clone your fork
3. Make changes
4. Push to your fork
5. Create Pull Request

For the DEVASC exam:

• Understand the difference clearly

---

17. Why Cloning Is Important in DevNet Context

In Cisco DevNet environments:

• API SDK repositories must be cloned
• Sample automation code must be cloned
• CI/CD pipelines clone repositories automatically
• Team collaboration requires cloning shared repos

Without cloning:

• No local development
• No version control workflow
• No automation pipeline execution

---

18. Key Exam Points to Remember

You must know:

• git clone copies a repository
• It downloads full history
• It sets up remote origin automatically
• Difference between HTTPS and SSH cloning
• Clone specific branch using -b
• Shallow clone using --depth
• Bare clone using --bare
• Clone vs download ZIP
• Clone vs fork
• Authentication basics

---

19. Summary (Easy Revision)

git clone:

• Creates a local copy of a remote repository
• Connects local repo to remote (origin)
• Downloads commit history
• Allows collaboration
• Used in development, automation, CI/CD

In simple words:

Clone = Start working on an existing project.