Master Version Control in

Web Development: An
Ultimate Guide
Learn about the importance of version control in web development and master project
source code management with this comprehensive guide. Stay ahead with tips and
tricks.

Written by RamotionApr 3, 202313 min read

Last updated: Feb 16, 2024

Table of Contents
1. Definition of version control
2. Importance of version control in web development
3. The Basics of Version Control
4. Benefits of Version Control Systems
5. Reasons to Use Version Control
6. Things to Look For in Version Control Software
7. Conclusion
Web development is a constantly evolving field, and developers must keep up with
the latest version tools and techniques. Version control is one of the most important
aspects of web development, and we'll go over what it is and why it's so important in
this blog.

Version control is a technique that tracks changes to code over time, allowing
developers to collaborate on a project and revert to previous versions as needed.
Version control is an essential tool for any web developer, whether they are working
on a small website or a large-scale web application.

In this blog, we'll go over the fundamentals of version control and how to use it
effectively in your web development projects. We'll also discuss the various version
control systems available and how to select the best one for your requirements. This
guide will provide valuable insights to help you stay ahead of the game, whether
you're a beginner or a web development expert. So, if you're ready to advance your
web development skills, let's get started!
Definition of version control
What is a version control?
Version control is a software development technique that lets multiple developers
work on the same set of source code files. Each time they save a file, the version
control system automatically saves a copy of the previous version, known as a
"checkpoint."
This way, if one developer accidentally deletes or overwrites another developer's
work, or if someone accidentally erases all of the files, the most recent copy can be
restored.

Version control systems also let you see who changed what and when; roll back to
previous versions; compare different versions (like when you're updating an existing
website); and collaborate with other developers on projects that have grown too large
for one person to handle alone. Version control also helps in case something goes
wrong with your website - for example, if it stops working because of server issues or
if there is malware on it. If you have a source control system in place, you can restore
the site to its last known good state and then use that as your starting point for fixing
things. This is especially important if you build websites for clients - they are going to
need an easy way to get their website back up and running if something goes wrong.
Importance of version control in web
development
Software developers and web developers are always in search of effective tools to
keep their work organized. Version control is one of the most useful tools that software
developers use, especially if they are involved in large software projects. It’s an
important tool that helps software developers manage their projects. It is a system that
keeps track of the changes made to files and allows users to revert back to previous
versions if they need to.

Assume you're working on a website with a team of developers. Everyone is working

on a different feature. By accident, one developer edited another developer's work
and pushed it to production. The website is currently down. You're attempting to
identify the problem and eventually locate it. However, you cannot go back in time and
prevent this from happening. What if you could at least go back to the previous
version of the source code? This is where version control comes in handy.

With version control, the code base can be managed and tracked easily. This means
that any changes made will be recorded and can be traced back to see who made
them and when they were made. It also helps to avoid conflicts between team
members as each person's changes are kept separate from each other's changes.

Version control systems are also useful for people who need a quick way to find the
most recent version of a file. If you've changed a document several times over the
course of a week and want to see what it looked like at the beginning, it can be difficult
to find out which version is the most current. A version control system makes this
process much easier by storing multiple versions of files in one place so they're easy
to access and compare.

The importance of having version control cannot be overstated as it allows developers

to work independently on the same project without fear of messing up each other's
work or stepping on each other's toes.

The Basics of Version Control

What is a version control system
Version control is a system that tracks changes to files and allows a user to revert to
older versions of the file.
It is used to maintain historical versions of files, documents, and websites. This allows
users to track changes to a document or file over time. Version control can also be
used to coordinate work on multiple versions of a project by multiple developers.

Version Control Systems (VCS) is designed specifically for software development

teams to manage changes to codebases in a collaborative environment. There are
many different types of VCS systems available, but they all have some basic
concepts in common.

Version control systems are especially useful for collaborative software projects
because they allow multiple users to work on the same files at the same time without
overwriting each others' changes. Many source control systems allow users to merge
conflicting changes into one final document so they don't have to worry about losing
any of their changes when other people edit the same document at different times.

Version control systems are often used in software development, but they can also be
useful for non-technical tasks. For example, if you’re writing a book or blog post, it’s
helpful to have an easy way to track changes over time. You might even use one
while working on a large project with other people—for example, if you’re collaborating
on a shared document or spreadsheet with others and need a way to keep track of
what everyone is doing.

How does version control work

Version control is a system that records changes to a file or set of files over time so
that you can recall specific versions later. It's most often used in software
development, but it has applications beyond that. The information stored in a version
control system can be used to restore older versions of files and documents, compare
versions, and collaborate with others on projects.
Version control systems are typically used by developers who are working on large
projects and need a way to track their work. A version control system provides an
easy way to see what changes have been made over time, so you can do code
review on the history of your project and see how it evolved from day one.

Here's how it works: when you make changes in your project files directory, those
changes are stored in a repository — usually with a version control system (VCS).
When you want to share your work with someone else, you can send them the
codebase from that repository. When they make their own changes, those changes
will be stored separately from yours, so that both of your versions can be compared
later on if necessary.

When you go back to an older version of your codebase, it's often called "checking
out" that version from the repository. This creates a new version of the codebase on
your machine that has all its files in the same state they were when you checked them
out — meaning they may not be up-to-date with any changes made since then.

Different types of version control systems

There are two types of version control systems, each with its own advantages and
disadvantages:
1. Centralized Version Control Systems (CVCS)

These systems keep all the files in a central repository, where only one person can
work on them at a time. With centralized source control, only one person can edit a file
at a time; others must wait for it to be checked out before they can work on it.

2. Distributed Version Control Systems (DVCS)

Distributed Version Control Systems (DVCS) are a type of version control system
(VCS) that are designed to allow several developers to work on the same codebase
at the same time. This means that multiple people with multiple computers can be
working on the same project in parallel, and when they push their changes to the
server, it will merge them together.

The most popular DVCS is Git, which was created by Linus Torvalds in 2005.

Benefits of Version Control Systems

Improved collaboration

Version control systems can help to improve collaboration and communication within
a software team. Through version control, it’s easy to see which changes have been
made by whom and when. This can help to avoid instances where multiple people
make different changes to the same file, causing confusion over who should be
responsible for which change.

Ease of managing changes

Version control systems make it easy to manage the changes that have been made
to a project. This can be useful when you need to go back and see what has changed
since a certain point in time, or if you want to revert back all of your changes at once.
Version control systems can help to manage changes by providing a central database
where all files and their associated revisions are stored. They also enable you to view
the changes that have been made over time, which means it’s easy to see how a
document has evolved from its original format into its current state.

Ability to revert to previous versions

If you make a change that you later regret, it’s easy to revert back to an earlier version
of the file. This is especially useful for documents that have been edited over time by
many different people, as it prevents any one individual from inadvertently changing
the formatting or content of a document.

This feature is also useful for situations where you want to try out a new format or
layout for your document, but want the ability to go back if it doesn’t work out. Version
history helps prevent users from making changes that cannot be undone because
they are unaware of how their actions might affect other people working on the same
document.

Enhanced security and backup

Version history is a useful feature for anyone who wants to protect their documents
from being inadvertently changed. It also helps make sure that important files don’t get
lost in case of a computer crash or other disaster. You can use version history to
create a backup of your files and then restore them if there is a problem.

With version history, you can see the date and time that each version was saved. You
can also restore a previous version of a file or folder if you need to do so. If you want
to make sure that your files are secure, then this tool will help.

Reasons to Use Version Control

Better organization of code

As a developer, you’ll find that it makes your code much easier to manage. You can
go back in time and see what changes have been made over the course of
development, and quickly revert changes if necessary. Version control is essential in
any large project and can help you avoid rewriting existing code. It also makes it easy
for your team members to work together on the same project without stepping on
each other’s toes.

Increased productivity

Version control allows you to focus on coding without having to worry about making
sure your changes don’t conflict with someone else’s. This frees up your brain power
and makes it easier for you to get things done quickly. You can also get feedback
from your team members more easily and make decisions together based on their
input.

Improved collaboration and teamwork

Version control helps you work with your team members more easily. You can
discuss issues and resolve them quickly without having to worry about stepping on
each other’s toes. This makes it easier for your development team to collaborate
effectively and move projects forward quickly.

Things to Look For in Version Control

Software
Version control software is a must-have for any development team. It can improve
collaboration and productivity, but it’s not always easy to choose the right one. If you
are looking to add version control to your development workflow, here are some
things to look for:

User-friendly interface

Version control software is a tool for developers, so it needs to be easy for them to
use. If it’s hard to configure or difficult to navigate, programmers won’t use it. The
version control software can be intimidating at first. But if you find one that has a user-
friendly interface, you’ll be able to get up and running quickly. It will also make it easier
for your team members to adopt the software as well.

Integration with other tools

Many version control platforms integrate with other tools, such as issue trackers and
wikis. This makes it easier for developers to use the software in their workflows. If you
want to add version control to your development workflow, look for a tool that supports
these integrations. If it’s hard to integrate version control with other software tools in
your development workflow, you’ll have a harder time getting the most out of it. For
example, you might need to use your version control software alongside code editors
like Visual Studio and Sublime Text in order to view changes and roll back versions of
your codebase.

Good support and documentation

Good documentation is also important. If you’re not sure how to use a tool, it can be
frustrating if there’s no documentation available for you to refer to. You should be able
to find clear instructions on how to install and configure your version control software,
as well as guidance on how it works with other software tools in your development
workflow.

A good example of this is GitHub’s documentation page, which provides a variety of

guides and tutorials that cover the basics of using Git as well as more advanced
features. In addition to providing documentation, it also offers support via email if you
run into any problems with your version control software.

Flexibility

The version control software can be used in many different ways, and there are many
different types of repositories. This means that you should be able to find a version
control system that works best for your needs. For example, Git is great if you want to
host your code on GitHub so that others can collaborate with you online.

Affordable pricing
Version control software is often free to use, but some systems have a paid version
that offers additional features. For example, GitLab offers both a free and paid version
of its product. The paid version allows you to host your code on the GitLab server
rather than using GitHub or Bitbucket, which can be helpful if you want more control
over your project.
https://www.ramotion.com/blog/version-control-in-web-development/

INFORMATION SHEET 1.3-1

Learning Objectives:

After reading this INFORMATION SHEET, LEARNER MUST be

able to:
1. Learn to assess and identify code versioning tools.
2. Identify the types of version control.

Overview:

Code versioning tools are assessed and identified

Version control software keeps track of every modification to the code in a special kind of database. If a
mistake is made, developers can turn back the clock and compare earlier versions of the code to help fix
the mistake while minimizing disruption to all team members.

Master Version Control in Web Development

Web development is a constantly evolving field, and developers must keep up with the latest version tools and
techniques. Version control is one of the most important aspects of web development, and we'll go over what it is and
why it's so important in this blog.

Version control is a technique that tracks changes to code over time, allowing developers to collaborate on a project
and revert to previous versions as needed. Version control is an essential tool for any web developer, whether they are
working on a small website or a large-scale web application.

In this blog, we'll go over the fundamentals of version control and how to use it effectively in your web development
projects. We'll also discuss the various version control systems available and how to select the best one for your
requirements. This guide will provide valuable insights to help you stay ahead of the game, whether you're a beginner
or a web development expert. So, if you're ready to advance your web development skills, let's get started!
Definition of version control

What is a version control?

Version control is a software development technique that lets multiple developers work on the same set
of source code files. Each time they save a file, the version control system automatically saves a copy of
the previous version, known as a "checkpoint."

This way, if one developer accidentally deletes or overwrites another developer's work, or if someone accidentally
erases all of the files, the most recent copy can be restored.

Version control systems also let you see who changed what and when; roll back to previous versions; compare
different versions (like when you're updating an existing website); and collaborate with other developers on projects
that have grown too large for one person to handle alone. Version control also helps in case something goes wrong
with your website - for example, if it stops working because of server issues or if there is malware on it. If you have a
source control system in place, you can restore the site to its last known good state and then use that as your starting
point for fixing things. This is especially important if you build websites for clients - they are going to need an easy way
to get their website back up and running if something goes wrong.
Importance of version control in web development

Software developers and web developers are always in search of effective tools to keep their work organized. Version
control is one of the most useful tools that software developers use, especially if they are involved in large software
projects. It’s an important tool that helps software developers manage their projects. It is a system that keeps track of
the changes made to files and allows users to revert back to previous versions if they need to.

Assume you're working on a website with a team of developers. Everyone is working on a different feature. By
accident, one developer edited another developer's work and pushed it to production. The website is currently down.
You're attempting to identify the problem and eventually locate it. However, you cannot go back in time and prevent
this from happening. What if you could at least go back to the previous version of the source code? This is where
version control comes in handy.
With version control, the code base can be managed and tracked easily. This means that any changes made will be
recorded and can be traced back to see who made them and when they were made. It also helps to avoid conflicts
between team members as each person's changes are kept separate from each other's changes.
Version control systems are also useful for people who need a quick way to find the most recent version of a file. If
you've changed a document several times over the course of a week and want to see what it looked like at the
beginning, it can be difficult to find out which version is the most current. A version control system makes this process
much easier by storing multiple versions of files in one place so they're easy to access and compare.
The importance of having version control cannot be overstated as it allows developers to work independently on the
same project without fear of messing up each other's work or stepping on each other's toes.
The Basics of Version Control

What is a version control system?

Version control is a system that tracks changes to files and allows a user to revert to older versions of
the file.

It is used to maintain historical versions of files, documents, and websites. This allows users to track
changes to a document or file over time. Version control can also be used to coordinate work on
multiple versions of a project by multiple developers.

Version Control Systems (VCS) is designed specifically for software development teams to manage
changes to codebases in a collaborative environment. There are many different types of VCS systems
available, but they all have some basic concepts in common.

Version control systems are especially useful for collaborative software projects because they allow
multiple users to work on the same files at the same time without overwriting each other’s' changes.
Many source control systems allow users to merge conflicting changes into one final document so they
don't have to worry about losing any of their changes when other people edit the same document at
different times.

Version control systems are often used in software development, but they can also be useful for non-
technical tasks. For example, if you’re writing a book or blog post, it’s helpful to have an easy way to
track changes over time. You might even use one while working on a large project with other people—
for example, if you’re collaborating on a shared document or spreadsheet with others and need a way to
keep track of what everyone is doing.

How does version control work?

Version control is a system that records changes to a file or set of files over time so that you can recall specific versions
later. It's most often used in software development, but it has applications beyond that. The information stored in a
version control system can be used to restore older versions of files and documents, compare versions, and
collaborate with others on projects.
Version control systems are typically used by developers who are working on large projects and need a way to track
their work. A version control system provides an easy way to see what changes have been made over time, so you can
do code review on the history of your project and see how it evolved from day one.
Here's how it works: when you make changes in your project files directory, those changes are stored in a repository
— usually with a version control system (VCS). When you want to share your work with someone else, you can send
them the codebase from that repository. When they make their own changes, those changes will be stored separately
from yours, so that both of your versions can be compared later on if necessary.

When you go back to an older version of your codebase, it's often called "checking out" that version from the
repository. This creates a new version of the codebase on your machine that has all its files in the same state they were
when you checked them out — meaning they may not be up-to-date with any changes made since then.

Different types of version control systems

There are two types of version control systems, each with its own advantages and disadvantages:

1. Centralized Version Control Systems (CVCS)

These systems keep all the files in a central repository, where only one person can work on them at a time. With
centralized source control, only one person can edit a file at a time; others must wait for it to be checked out before
they can work on it.

2. Distributed Version Control Systems (DVCS)

Distributed Version Control Systems (DVCS) are a type of version control system (VCS) that are designed to allow
several developers to work on the same codebase at the same time. This means that multiple people with multiple
computers can be working on the same project in parallel, and when they push their changes to the server, it will
merge them together.

Benefits of Version Control Systems

Improved collaboration

Version control systems can help to improve collaboration and communication within a software team. Through
version control, it’s easy to see which changes have been made by whom and when. This can help to avoid instances
where multiple people make different changes to the same file, causing confusion over who should be responsible for
which change.

Ease of managing changes

Version control systems make it easy to manage the changes that have been made to a project. This can be useful
when you need to go back and see what has changed since a certain point in time, or if you want to revert back all of
your changes at once. Version control systems can help to manage changes by providing a central database where all
files and their associated revisions are stored. They also enable you to view the changes that have been made over
time, which means it’s easy to see how a document has evolved from its original format into its current state.

Ability to revert to previous versions

If you make a change that you later regret, it’s easy to revert back to an earlier version of the file. This is especially
useful for documents that have been edited over time by many different people, as it prevents any one individual from
inadvertently changing the formatting or content of a document.

This feature is also useful for situations where you want to try out a new format or layout for your document, but want
the ability to go back if it doesn’t work out. Version history helps prevent users from making changes that cannot be
undone because they are unaware of how their actions might affect other people working on the same document.

Enhanced security and backup

Version history is a useful feature for anyone who wants to protect their documents from being inadvertently
changed. It also helps make sure that important files don’t get lost in case of a computer crash or other disaster. You
can use version history to create a backup of your files and then restore them if there is a problem.

With version history, you can see the date and time that each version was saved. You can also restore a previous
version of a file or folder if you need to do so. If you want to make sure that your files are secure, then this tool will
help.

Reasons to Use Version Control

Better organization of code

As a developer, you’ll find that it makes your code much easier to manage. You can go back in time and see what
changes have been made over the course of development, and quickly revert changes if necessary. Version control is
essential in any large project and can help you avoid rewriting existing code. It also makes it easy for your team
members to work together on the same project without stepping on each other’s toes.

Increased productivity

Version control allows you to focus on coding without having to worry about making sure your changes don’t conflict
with someone else’s. This frees up your brain power and makes it easier for you to get things done quickly. You can
also get feedback from your team members more easily and make decisions together based on their input.

Improved collaboration and teamwork

Version control helps you work with your team members more easily. You can discuss issues and resolve them
quickly without having to worry about stepping on each other’s toes. This makes it easier for your development
team to collaborate effectively and move projects forward quickly.

Things to Look for in Version Control Software

Version control software is a must-have for any development team. It can improve collaboration and productivity, but
it’s not always easy to choose the right one. If you are looking to add version control to your development workflow,
here are some things to look for:

User-friendly interface

Version control software is a tool for developers, so it needs to be easy for them to use. If it’s hard to configure or
difficult to navigate, programmers won’t use it. The version control software can be intimidating at first. But if you find
one that has a user-friendly interface, you’ll be able to get up and running quickly. It will also make it easier for your
team members to adopt the software as well.

Integration with other tools

Many version control platforms integrate with other tools, such as issue trackers and wikis. This makes it easier for
developers to use the software in their workflows. If you want to add version control to your development workflow,
look for a tool that supports these integrations. If it’s hard to integrate version control with other software tools in your
development workflow, you’ll have a harder time getting the most out of it. For example, you might need to use your
version control software alongside code editors like Visual Studio and Sublime Text in order to view changes and roll
back versions of your codebase.

Good support and documentation

Good documentation is also important. If you’re not sure how to use a tool, it can be frustrating if there’s no
documentation available for you to refer to. You should be able to find clear instructions on how to install and
configure your version control software, as well as guidance on how it works with other software tools in your
development workflow.

A good example of this is GitHub’s documentation page, which provides a variety of guides and tutorials that cover the
basics of using Git as well as more advanced features. In addition to providing documentation, it also offers support via
email if you run into any problems with your version control software.
Flexibility

The version control software can be used in many different ways, and there are many different types of repositories.
This means that you should be able to find a version control system that works best for your needs. For example, Git is
great if you want to host your code on GitHub so that others can collaborate with you online.

Affordable pricing

Version control software is often free to use, but some systems have a paid version that offers additional features. For
example, GitLab offers both a free and paid version of its product. The paid version allows you to host your code on the
GitLab server rather than using GitHub or Bitbucket, which can be helpful if you want more control over your project.

Reference:
https://www.ramotion.com/blog/version-control-in-web-development/

Self-Check 1.3-1

A: Things to look for in a version control software.

 1. _________________________________
2. _________________________________
3. _________________________________
4. _________________________________
5. _________________________________

B: Reason to use version control.

1. _________________________________
2. _________________________________
3. _________________________________

C: Benefits of version control system.

1. _________________________________
2. _________________________________
3. _________________________________
4. _________________________________

Answer Key 1.3-1

A:
 1. User-friendly interface
2. Integration with other tools
3. Good support and documentation
4. Flexibility
5. Affordable pricing:

B:

1. Better organization of code

2. Increased productivity
3. Improved collaboration and teamwork

C:

1. Improved collaboration
2. Ease of managing changes
3. Ability to revert to previous versions
4. Enhanced security and backup

INFORMATION SHEET 1.3-2

Learning Objectives:

After reading this INFORMATION SHEET, LEARNER MUST be

able to:
1. Learn to select and install code versioning tool.
2. Identify the different code versioning tool.

Overview:

Code versioning tool is selected and installed

Version control software keeps track of every modification to the code in a special kind of database. If a
mistake is made, developers can turn back the clock and compare earlier versions of the code to help fix
the mistake while minimizing disruption to all team members.

Overviews of the 5 Best Version Control Tools

Here’s a brief description of each version control tool that showcases each software’s best use case,
outstanding features, and some pros and cons. I’ve also included screenshots to give you a snapshot
of their user interface too.

1. New Relic

Best version control tool for version analysis

 Free plan available
 From $49/user/month
 New Relic is a software analytics product that's all about providing real-time insights into your
software performance. It's not just a version control tool, it's more like a Swiss Army knife for your
software, helping you monitor, troubleshoot, and optimize your applications.

Why I Picked New Relic: New Relic's mobile monitoring involves a comprehensive examination of the
adoption and operational effectiveness among different iterations of your application. This
encompasses key versions distinguished by factors such as interaction duration, active user sessions,
and error occurrences. On the Versions page, there exists a table that juxtaposes each version based
on its creation date, average memory and CPU usage, mean sessions per minute, as well as the
average requests per minute (RPM) per active application. For more in-depth insights into a particular
version, the option to delve into supplementary details is also available.
New Relic Standout Features & Integrations
Features include the ability to drill down into your data. You can get really granular with your analysis,
which is super helpful when you're trying to troubleshoot a specific issue or optimize a particular
aspect of your software. Plus, it's got some helpful, custom alerting capabilities, so you can stay on
top of any issues that arise.
Integrations include over 500 apps that include cloud platforms like AWS, Google Cloud, and
Microsoft Azure, CI/CD tools like Jenkins, CircleCI, and Travis CI, communication tools like Slack and
PagerDuty, and other monitoring and analytics tools like Grafana, Datadog, and Splunk. It also has an
API you can use to build custom integrations.

Pros and cons

Pros:
 Wide range of monitoring capabilities
 AI-powered anomaly detection and intelligent alerting
 Integrates seamlessly with popular dev tools

Cons:
 Added complexity from reliance on agents installed on application servers
 Bigger focus on reporting rather than facilitating actions

2. Datadog

Best for infrastructure and container monitoring

 14-day free trial
 From $15/user/month (billed annually)
 Datadog is a leading monitoring and security platform that provides the monitoring capabilities you
need to see inside your infrastructure at any scale and from anywhere.
Why I picked Datadog: This platform is on my list due to its unique infrastructure monitoring
capabilities. It gives you visibility into your infrastructure performance and lets you know when there
is a need to optimize anything with minimal maintenance and unparalleled breadth of coverage.
Datadog offers real-time visibility, metrics, visualizations, and alerts to help you keep track of your
cloud or hybrid environments and manage changes effectively.
Datadog Standout Features and Integrations
Standout features include container monitoring, CI visibility, and database monitoring. Datadog
provides your agile team with comprehensive visibility into your CI environments, helping you to
streamline your CI/CD workflows. It helps you track the health and performance of your codebase and
also allows you to monitor your CI data by repository, branch, or commit. Comprehensive CI visibility
makes it easier to fix issues, reduce CI costs, and ship better products.
Integrations are available with a wide range of third-party tools, including Slack, Google Workspace,
Microsoft 365, GitHub, Jira, Microsoft Teams, Rippling, Zendesk Suite, Google Cloud, and MySQL.

Pros and cons

Pros:
 Good alerting system
 It improves collaboration
 Friendly pricing

Cons:
 Slow response from the support team
 Steep learning curve

3. AWS CodeCommit

Best for collaborating on code and customizing user-specific access to your repositories
  Free plan available
 Pricing upon request

AWS CodeCommit is a managed source code control service. It allows you to host very scalable private
Git repositories and provides collaborative features for working together on code.
Why I picked AWS CodeCommit: It makes things a lot easier for developers by getting rid of the need
to host, maintain, backup, or scale their source control infrastructure. AWS CodeCommit improves
collaboration, enabling development teams to boost productivity. You can implement collaborative
workflows, such as code review and feedback.
The software allows you to control who can execute changes to certain branches. This is a project
management feature that enables you to ensure that only authorized users are permitted to alter
some sensitive parts of your code repository. It reduces conflicts and improves efficiency.
AWS CodeCommit Standout Features and Integrations
Standout features: AWS CodeCommit allows you to build up to a thousand repositories by default.
You can store and version any kind of file and create up to 25,000 more repositories by request. It
offers an outstanding alerting solution, which helps you get notified when there is an event affecting
your repositories. Additionally, AWS CodeCommit gives you control over your software projects by
allowing you to keep using your favorite development environments and DevOps toolset.
Integrations include SAS Visual Analytics, SAS Customer Intelligence 360, Relution, Kaholo, Eclipse,
Visual Studio, AWS Cloud9, Sourcegraph, Jira Cloud, and Tenable.

Pros and cons

Pros:
 Flexible pricing model
 Get started for free with AWS Free Tier
 Free AWS training

Cons:
 Complex UI for new users
 Configurations are a bit difficult
4. Git

Best free and open-source version control system

 Free to Use

This is a free and open-source distributed version control tool designed to help developers manage
coding projects (small and large) with speed and efficiency.
Why I picked Git: Git is on my list because it offers industry-standard version control capabilities for
free. I also considered Git because global giant companies, like Google, Microsoft, and Netflix, are
using it. Git is easy to learn and has a very small footprint with ultra-fast performance.
Git is designed from the ground up to perform with exceptional speed and efficiency. Most of its
operations are executed locally, making it very fast since there is no need to communicate with a
server somewhere. It can handle large repositories as it was built to work on the Linux kernel. In
addition, the overhead of runtimes that come with high-level languages is reduced since Git is written
in C.
Git Standout Features and Integrations
Standout features that set Git apart include cheap local branching and convenient staging areas. Git’s
branching and merging model allows you to create multiple local branches that are entirely
independent of each other. This empowers you to execute frictionless context switching, role-based
codelines, feature-based workflow, and disposable experimentation.
Git has an outstanding feature known as Staging Area or Index. Staging Area is an intermediate area
where commits can be formatted and reviewed prior to completing the commit. This capability
enables developers to quickly stage some of their files and commit them without committing all of the
other files that are modified in their working directory.
Integrations include Datadog, GitHub, TIBCO Data Virtualization, Visual Studio Code, Coalesce, Telerik,
TestComplete, and Sisense.

Pros and cons

 Pros:
 Very secure
 An active user community
 Available for free

Cons:
 Learning and mastering Git takes time
 Resolving merge conflicts can be tedious

5. Subversion

Best centralized version control system for file locking and merge tracking
 Free to Use

Apache Subversion is a feature-rich version control system originally designed to replace CVS. It's an
enterprise-level, centralized, open-source version control tool that supports the needs of a wide
variety of users and projects.
Why I picked Subversion: In addition to industry-leading version control capabilities, Subversion
allows file locking. This feature lets you lock files so that developers can be alerted when other users
are attempting to edit the same file. This prevents the modification of certain files by unauthorized
users.
The tool also offers merge tracking, which provides automated assistance with managing the flow of
modifications between lines of development and with the merging of branches back into their
sources.
Subversion Standout Features and Integrations
Standout features include interactive conflict resolution, atomic commits, and cheap branching and
tagging. Subversion supports interactive conflict resolution as one of the ways of fixing conflicting
changes. Atomic commits entail that no part of a commit becomes active or takes effect until the
entire commit has succeeded. Moreover, common operations are versioned, including copying,
deleting, and renaming.
 Integrations include ReqView, Alert Logic MDR, TIBCO Data Virtualization, Coverity, Collaborator,
Visual Expert, C++Builder, devZing, Kanbanize, and Allstacks.

Pros and cons

Pros:
 Easy to use
 Committing and merging code is pretty straightforward
 Available for free

Cons:
 Tracking the merges can be complex
 Sometimes, it takes a long time to load changes

Reference:
https://theqalead.com/tools/best-version-control-tools/#full-listing-1024444

Task Sheet 1.3-2

Title: Code versioning tool is selected and installed

Performance Objective: Install Git, the selected versioning tool.

Tools/PPE: I n t e r n e t c o n n e c t i o n
Equipment : C o m p u t e r U n i t
Steps/Procedure:

1. Go to the website https://git-scm.com/?r=qal-bvct.

2. Download Git for your respective OS.
3. Double click on the file downloaded.
4. Click “Run” on the Security Warning window.
5. Click “Yes” on the User Account Control.
6. Follow the setup process.
7. Run Git.

After installing Git go to the following site below for tutorial on how to use:
https://git-scm.com/docs/user-manual
 https://git-scm.com/book/en/v2

Assessment Method: Performance Demonstration.

PERFORMANCE CRITERIA CHECKLIST JOB SHEET 1.3-2

Code versioning tool is selected and installed

Trainee’s Name: Date:

CRITERIA YES NO N/A

1. Did you Go to the website https://git-scm.com/?r=qal-bvct?
2. Did you download Git for your respective OS?
3. Did you double click on the file downloaded?
4. Did you click “Run” on the Security Warning window?
5. Did you click “Yes” on the User Account Control?
6. Did you follow the setup process?
7. Did you run Git?

Comments/Suggestions
 Trainer’s Signature: Date: ____________

INFORMATION SHEET 1.3-3

Learning Objectives:

After reading this INFORMATION SHEET, LEARNER MUST be

able to:
1. Learn to use code versioning tools.

Overview:

Code versioning tool is used in web development process.

In software development, versioning allows development teams to keep track of changes they make to
the project code. The changes may include new functions, features or bug fixes.
What is Git?

Git is a Distributed Version Control System (DVCS) used to save different versions of a file (or set of files)
so that any version is retrievable at will.

Git also makes it easy to record and compare different file versions. This means that the details about
what changed, who changed what, or who initiated an issue are reviewable anytime.

But if Git is a Distributed Version Control System, what exactly do those terms mean?

What does “distributed” mean?

The term “distributed” means that whenever you instruct Git to share a project’s directory, Git does not
only share the latest file version. Instead, it distributes every version it has recorded for that project.

This "distributed" system is in sharp contrast to other version control systems. They only share whatever
single version a user has explicitly checked out from the central/local database.
Okay, so “distributed” means distribute all — not just selected few — versions of a project’s files that Git
has recorded. But what exactly is a version control system?

What is a Version Control System?

A Version Control System (VCS) refers to the method used to save a file's versions for future reference.

Intuitively, many people already version control their projects by renaming different versions of the
same file in various ways
like blogScript.js, blogScript_v2.js, blogScript_v3.js, blogScript_final.js, blogScript_definite_final.js, and
so on. But this approach is error-prone and ineffective for team projects.
Also, tracking what changed, who changed it, and why it was changed is a tedious endeavor with this
traditional approach. This illuminates the importance of a reliable and collaborative version control
system like Git.
However, to get the best of Git, it is essential to understand how Git handles your files.

Files states in Git

In Git, there are three primary states (conditions) in which a file can be: modified state, staged state,
or committed state.

Modified state

A file in the modified state is a revised — but uncommitted (unrecorded) — file.

In other words, files in the modified state are files you have modified but have not explicitly instructed
Git to monitor.

Staged state

Files in the staged state are modified files that have been selected — in their current state (version) —
and are being prepared to be saved (committed) into the .git repository during the next commit
snapshot.

Once a file gets staged, it implies that you have explicitly authorized Git to monitor that file’s version.

Committed state

Files in the committed state are files successfully stored into the .git repository.
Thus, a committed file is a file in which you have recorded its staged version into the Git directory
(folder).

Note: The state of a file determines the location where Git will place it.

File locations

There are three key places versions of a file may reside while version controlling with Git: the working
directory, the staging area, or the Git directory.

Working directory
 The working directory is a local folder for a project's files. This means that any folder created anywhere
on a system is a working directory.

Note:

 Files in the modified state reside in the working directory.

 The working directory is different from the .git directory. That is, you create a working directory while
Git creates a .git directory.
 Check out this comparison article for more differences between the two repositories.

Staging area

The staging area — technically called “index” in Git parlance — is a file, usually located in
the .git directory, that stores information about files next-in-line to be committed into the .git directory.

Note:

 Files in the staged state reside in the staging area.

Git directory

The .git directory is the folder (also called “repository”) that Git creates inside the working directory you
have instructed it to track.

Also, the .git folder is where Git stores the object databases and metadata of the file(s) you have
instructed it to monitor.

Note:
 The .git directory is the life of Git — it is the item copied when you clone a repository from another
computer (or from an online platform like GitHub).
 Files in the committed state reside in the Git directory.

The basic Git workflow

Working with the Git Version Control System looks something like this:
1. Modify files in the working directory.
Note that any file you alter becomes a file in the modified state.
2. Selectively stage the files you want to commit to the .git directory.
Note that any file you stage (add) into the staging area becomes a file in the staged state.
Also, be aware that staged files are not yet in the .git database.
Staging means information about the staged file gets included in a file (called "index") in
the .git repository.
3. Commit the file(s) you have staged into the .git directory. That is, permanently store a snapshot of the
staged file(s) into the .git database.

Note that any file version you commit to the .git directory becomes a file in the committed state.

The gist thus far

The long and short of all the discussion thus far is that Git is a brilliant version control system for
competent versioning, management, and distribution of files. Check out this simple guide to learn how
to use Git efficiently.

But, hang on a sec, if Git helps to effectively manage and distribute different versions of a project's file,
what is GitHub's purpose?

Reference:
https://www.freecodecamp.org/news/git-and-github-overview/#:~:text=GitHub
%20%E2%80%94%20Primary%20function,for%20hosting%20Git%20repositories%20online.
 Self-Check 1.3-3

True or False: Write the letter T if the statement is true and F if the statement is false on the space
provided.

_____________ 1. The long and short of all the discussion thus far is that Git is a brilliant
version control system for competent versioning, management, and
distribution of files.
_____________ 2. The .git directory is the life of Git — it is the item copied when you clone a
repository from another computer (or from an online platform like
GitHub).
_____________ 3. The .git directory is the folder (also called “respiratory”) that Git creates
inside the working directory you have instructed it to track.
_____________ 4. The staging area — technically called “index” in Git parlance — is a file,
usually located in the .git directory, that stores information about files
next-in-line to be committed into the .git directory.
_____________ 5. Files in the committed state are files successfully stored into
the .git repository.
_____________ 6. A file in the modified state is a revised — but uncommitted (unrecorded)
— file.
_____________ 7. There are two key places versions of a file may reside while version
controlling with Git: the working directory and the staging area.
_____________ 8. A Version Control System (VCS) refers to the method used to save a file's
 versions for future reference.
_____________ 9. The term “distributed” means that whenever you instruct Git to share a
project’s directory, Git does not only share the latest file version.
_____________ 10. Git is a Distributed Version Control System (DVCS) used to save different
versions of a file (or set of files) so that any version is retrievable at will.

Answer Key 1.3-3

1. T
2. T
3. F
4. T
5. T
6. T
7. F
8. T
9. T
10. T