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 arti-facts.

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, and merge changes from multiple developers into a single code base.

Source control systems also provide a safety net for developers, allow them to roll back changes, recover lost code, and 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 regard 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.

If you are interested in joining our organisation as a developer it is important that you have a good understanding of them. We mostly use GIT as the source control system in our org. If you are an aspiring developer. Make suer you go through the following and have a good understanding of git.

Get Familiar with following commands

make sure you 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