Github is an online platform built to promote code hosting, version control and collaboration among individuals working on a common project. Projects can be handled from anywhere through the platform. (Hosting and reviewing code, managing projects and building software with other developers around the world) The GitHub platform offers project handling to both open-source and private projects.
Features offered in regards to team project handling include; GitHub Flow and GitHub Pages. These functions make it easy for teams with regular deployments to in handling the workflow. GitHub pages, on the other hand, provides a place for showcasing open source projects, displaying resumes, hosting blogs among others.
Individual projects can also be easily handled with the aid of GitHub as it provides essential tools for projects handling. It also makes it easier to share one's project with the world.
Signing Up for GitHub and Starting a Project
When starting a new project on GitHub, you must first create an account here using your email address.
Then, on verification of the address, the user will be automatically logged into their GitHub account.
1. Creating a Repository
After which, one is taken to the next page that allows for the creation of a repository. A repository is a storage for all project files including revision history. Repositories are either, public or private. Public repositories are visible to everyone, however, the owner chooses an individual who can commit to the project. On the other hand, private repositories provide extra control to who can view the repositories. As a result, public repositories are suitable for open source software projects while private repositories are mostly suited to private or closed source projects.
2. Adding a Branch
In GitHub, branches are a way of working on various versions of a single repository simultaneously. By default, any single repository created is assigned a branch called MASTER and it is considered the final branch. In GitHub, branches are useful in experimenting and editing of repositories before committing them to the master (Final branch).
For personal suitability, it is always necessary to add several other branches to suit different projects. Creating a branch off the master branch is the same as copying the master as it was at that instant.
Creating branches is similar to saving a single file in different versions. This is achieved by renaming according to the task being carried out on a particular repository.
Branches also prove useful in keeping bug fixes and feature work separated from the master branch. After necessary changes, these branches are merged into the master branch.
To make a branch after creating the repository;
3. Making and Committing Changes
This step provides guidelines on how changes are made to a repository and saved. In GitHub, commits is the word used to refer to saved changes. Each commit is also associated with a commit message that contains a history of the saved changes and why particular changes were made. This makes it easy for other contributors to follow what was done and why.
To make and commit changes to a repository, the following are the steps;
4. Opening a Pull Request
Pull request is a feature that allows a contributor to propose and request someone to review and merge certain changes to their branch. Pull requests also show the difference (diffs) from several branches. Changes, additions, and subtractions are usually shown in red and green colors. Pull requests can be started as soon as a commit is made. Even when the code is not finished.
To open a pull request:
The user can demonstrate this by trying to create and saving a pull request.
5. Merging the Pull Request
This final step involves bringing readme-edits and master branches together. The merge Pull button shows up in case the readme-edits and the master branch do not conflict.
When merging pulls, there is need to ensure that the comments and other fields are filled properly. To merge pulls: