Archives
- Newer posts
- April 2024
- November 2023
- October 2023
- August 2023
- May 2023
- February 2023
- October 2022
- August 2022
- July 2022
- May 2022
- April 2022
- March 2022
- February 2022
- June 2020
- March 2020
- February 2020
- January 2020
- December 2019
- November 2019
- October 2019
- September 2019
- August 2019
- July 2019
- June 2019
- May 2019
- April 2019
- March 2019
- February 2019
- January 2019
- December 2018
- November 2018
- October 2018
- September 2018
- August 2018
- July 2018
- June 2018
- May 2018
- April 2018
- March 2018
- February 2018
- January 2018
- December 2017
- November 2017
- October 2017
- September 2017
- August 2017
- July 2017
- June 2017
- May 2017
- April 2017
- March 2017
- February 2017
- January 2017
- August 2016
- June 2016
- April 2016
- March 2016
- February 2016
- January 2016
- July 2015
- June 2015
- Older posts
Using Source Control
In our industry, we are highly dependent on storage devices in order to save our data. With the growing need for technology, we also need more storage. While working in a team, we share our code by making use of ‘Source Control’ to access the code from anywhere at any point of time and keep track of the modified files (versions) by using commits.
An individual team member can make a copy of the project on his/her PC and can work on it locally. Once the code is ready to be moved to the main repository, the source control helps in tracking the modified files (versions).
One of the widely used version control software is git. Each user needs to have a git account with a password and a private key.
We can create separate (multiple) branches on the local system and whatever we modify on the local branch is not reflected on the main (master) branch until we push it. Sometimes, conflicts might occur while merging the various branches, which can be fixed just by keeping the code that is required and deleting the unwanted code manually from the particular file.
Some of the advantages of using Source Control are:
- Allows comparison of files, identifying the differences, and merging the final change that took place.
- Keeps track of the versions.
- Multiple developers can work on a project at the same time.
- Saves time in identifying the issues.
- We can also check who has worked on the modified file (using blame command).
- Cloning of the repository is easy.
- It also keeps logs of the files previously committed.
- Making a patch for a small fix.
It is necessary for any organization to maintain a Source Control in order to retain the project data in the future and smooth flow of the projects.