Git allows developers at AnswerCrowd to track unlimited code changes through version control. It benefits developers by allowing them to work on files without overwriting each other's changes through branching. Git also provides confidence to developers to make risky changes by allowing easy rollbacks. Git synchronizes code across production, pre-production, and development environments. The document reaffirms Git's powerful ability to manage code revisions and transform a project into a robust code repository.

1. Git implementationreport
Harnessing the power of “GIT” the version control system, to allow AnswerCrowd to keep track
of unlimited code changes
What are the benefits?
● GIT allows developers to work on files without losing changes. This was previously a big
problem when fixes were getting lost/overwritten by other fixes as there was no system
to track the status.
● ‘Branching’ enables the developer to work on an feature enhancement or bug without
effecting the ‘trunk’ of the code. Previously what was happening is that if a feature was
not completed successfully before the next feature was required (think urgent bugfix)
then development would be stuck in limbo! Often then the changes would be lost, left
behind or more time was spent trying to remember what lines of code were changed
within each file.
● GIT provides confidence to the developer to strip out code that no longer works and to
make risky changes, as rolling back to a working copy is done with a double click.
Previously one would have to keep a record of each change that was made manually,
which is slow and prone to human error. It’s automatic now.
● GIT ‘synchronises’ the code with a few commands to all the AnswerCrowd
environments. Environments include:
○ Production which is the live working app
○ Pre-production which is the testing environment that is used to confirm changes
are working before pushing to production.
○ Development, located on the developer's machine which is a playground for
rapid development of features and bug fixes.
What did you learn or re-affirm?
● Reaffirmed GIT’s powerful ability to manage code revisions and transform a project into
an awesome repository of potential
Photo’s/Documents/Logos/Screenshots

2. Above the red line is a separate branch called “multiselectdrop” which is development of a
requested enhancement. The blue line is the master development line which is in current use.
Recently this blue line took priority when a bug was raised regarding a mail delay issue. Once
that issue has been resolved the red and blue line will merge together and live happily ever
after… until another coloured line appears and the adventure starts all over again!

3. There is a steep learning curve if a developer has never used a version control system, however
it is well worth it and unlikely you will ever want to go back. With the help of a GUI such as
SourceTree for Windows/Mac it’s a whole lot easier.
Bridh Athanatos
Web Developer