THE PROCESS

GitHub

GitHub

GitHub is a web-based Git version control repository and Internet hosting service. It offers all of the distributed version control and source code management functionality of Git as well as adding its own features. It provides access control and several collaboration features such as bug tracking, feature requests, task management, and wikis for every project.

The GitHub Repository we create at the begin of each project may be created following the Github documentation or forking the alpha repository which include samples for all the configuration files we need.

Collaborators

The collaborators added to each repository are

  • All members of the development team
  • InfoRBot
  • At least one issue approver 1(a member of the QA unit)

Other personnel is added upon their request. We welcome all the users as collaborators.

Labels

The Labels below are added to the repository

  • Accepted
  • Approved
  • Confirmed
  • Endorsed
  • Enhancement
  • Feature
  • Fix
  • Nullified
  • Payoff
  • Rejected

Other labels may be added according to the needs.

Projects

The Development Project is created to the repository. The project has the column below

  • Backlog
  • In Progress
  • Completed
  • Done

It is used to keep track of issue implementation and approval.

Branch Protection

When protecting the master branch we activate the options below

  • Require pull request reviews before merging
  • Dismiss stale pull request approvals when new commits are pushed
  • Require status checks to pass before merging
  • Require branches to be up to date before merging
  • Include administrators

Status checks are automatically sent, along side additional data, by the integrated services once they finish running. Their values can be either pass or failure and they can be required or optional.

The status checks currently in place are

  • codeclimate (code quality) [Required]
  • codeclimate/diff-coverage [Required]
  • codeclimate/total-coverage [Required]
  • continuous-integration/codeship or ci/circleci [Required]
  • codeclimate/coverage

With our setup, checks marked as required must pass in order to be able to merge an issue branch into master.

#####Notes:

  1. For more details regarding issue owners may be found at the issue management page.