Skip to content
Home » Learning Source Control systems – GIT

Learning Source Control systems – GIT

Source control systems, also known as version control systems, are a type of software tool used in program development to manage changes to the source code and other software artefacts.

Source control system track and manage change to files and directories, recording who made the changes, when they were made, and what was changed. They allow developers to

  • Collaborate on code changes
  • Work on multiple versions of the code simultaneously – using branches
  • Merge changes from multiple developers into a single code base.
  • Roll back changes
  • Recover lost code
  • Maintain a complete history of all changes to the code base.

Some popular source control systems include Git, Subversion, Mercurial, and Perforce. The source code system is regarded as a best practice in software development, as it helps teams collaborate more effectively, maintain code quality, and reduce the risk of errors and bugs in the code base.

In this blog, we share some basics of Git. Git is the most commonly used source control system. If you are an aspiring developer, it is important that you have a good understanding of GIT.

Go through the following links to have a good understanding of git.

Get Familiar with following commands

Create an account on github / gitlab .

Create a repository and practice these commands and use and understand them.

  1. commit
  2. push
  3. pull
  4. rebase
  5. stash
  6. add
  7. checkout
  8. Create branch
  9. merge branch
  10. Delete branch
  11. forking
  12. Raising a Pull request


  1. Create an account on
  2. Create a repository on name it cegees-training-[your-name]
  3. – you can request to join this group.
  4. Configure your ssh keys –
  5. Invite the following group (ceegees-training) as a developer to the repository
  6. Create a readme file
  7. Create a branch develop
  8. Switch to develop
  9. Make changes on readme on develop
  10. commit the changes and push the same
  11. switch to master
  12. Make changes on the readme file
  13. Commit changes to master
  14. Merge develop to master –
  15. Resolve conflicts