How we utilised Git

General

Git was used to track all changes and contributions, to keep track of progress as well as Version Control. It was also configured such that all Pull Requests to the Master branches requires a Review from at least one other group member, so that at least one other person had assessed either the code or documentation to increase the chance of catching any errors before they became a problem.

Documentation

To augment our Document Version Control tables we also tracked all of our documentation with Git using a GitHub repository, to ensure that all members had the same view of the documentation, to ensure that document versions did not become mixed or confused, and to allow multiple people to work on the same document at the same time with easy conflict resolution. As the majority of our documents are written in LaTeX, this system works very well.

Logs

master

BCBranch

DavidWorkingBranch

SamBranch

PeterWorkBranch

reduce-spec

FinanceReport


Product Source

To control and distibute our sources, we used a centralised GitHub repository. This allows every member to have an upto date copy of the sources, easily work on the same file as another member without significant overhead, and gives the project management a quick overview of progress and member input.

Logs

master

BCBranch

DavidDev

feature-edit

feature-graphics

feature-network

fix-image_download

feature-tools

feature-script

feature-save

feature-playable

feature-test

fix-rework_controller_api

fix_WindowPath

linting-branch

sambranch


HTML Tour

The HTML Tour is also in a GitHub Git repository. This provides hosting, so sharing the pages with the group is simple.

Logs

master