Git Flow Exercise
An exercise for learning the git-flow branching model. This exercise will walk your team through a full release cycle for an example application.
Hand in
When you finish all steps, take a screenshot of your git log with all branches visible either useing ex. git log --oneline --graph --all, or a visual git tool. Take a screenshot only of your groups commits, nothing else and compare it to the drawing on this page introducing git flow.
Upload a screenshot of your log on the course website. One person of the group posts the url and image file. I will then look at your fork on Github since it's linked to mine, I will find it.
Scenario
The print magazine Flavor has asked your firm to build and maintain an app so they can share recipes with their hungry audience.
The typical development cycle for the project is as follows:
- On the 1st of every month, your team receives a list of each writer's pick for recipe of the month.
- On the 15th of every month, the new version of the app is pushed to a staging server where the magazine's editors can do a final review.
- On the last day of the month, the new version of the app is pushed to production.
Development for v1.0.0 of this project began in January. It is now the beginning of February and the development cycle for v1.1.0 of the app has begun.
Getting Started
Your team is made up of two developers. Each of you will contribute new content to the project from your computers and also review the other developers contribution.
Follow Along
Please leave this repository open in a browser tab so that you can follow along with the activities without referring to the presenter's screen.
Project Structure
- Application code can be found in the
/app/folder. - The application contains a file named
VERSIONthat contains the major, minor, and patch numbers for the project. - Source files are written in markdown and can be identified by the
.mdfile extension.
Next
Next we will walk through the process of creating a GitHub Fork and local clone of this repository.