This file is a fantasy readme for an tool that doesn't exist yet. I wrote it in an attempt to apply readme driven development. The idea is to force yourself to define a vision for your product/tool/whatever before starting to build anything.
Jimbo is working on his project codenamed Electric Nachos. He makes a final change, observes that all tests are passing and is ready to deploy. He commits his changes:
git add . && git commit -m "ready to go"
Being a cautious, sensible fellow Jimbo wants to deploy to his test environment first. He switches to his test environment branch:
git checkout test
and merges his changes
git merge master
and finally pushes his changes
git push origin test
Jimbo counts to ten, then pops open a browser and checks the Electric Nachos test environment. His changes are already there
In the Electric Nahcos test environment Jimbo is running Git Deploy. Git Deploy is a service that Jimbo has configured with a reference to a directory containing the Electric Nachos git repo. From that Git Deploy can detect the url of Jimbo's master repo. Git deploy is also configured to know the name of the branch it should deploy (in this case test). Git deploy monitors the test branch for changes. When a change is detected it pulls the update into the local repository. It then looks for a script called test.gitdeploy and executes it.