daafonsecato / git-github-ramp

An exercise for Git, GitHub and git-flow

Git Flow Katas Exercise

An exercise for learning the git-flow branching model, inspired in a previous exercise. This exercise will walk your team through a full release cycle for an example application.

OBJECTIVES

1. Apprehend basic and most used Git commands
2. Apprehend GitHub
3. Extra: Apprehend Git Flow

Background

The print magazine Onlyrics has asked your firm to build and maintain an app so they can share song information and fun facts with their rhythmic audience.

The typical development cycle for the project is as follows:

• On the 1^st of every month, your team receives a list of each writer's picks for the song of the month.
• On the 15^th 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 this project began in June. It is now the beginning of July and the development cycle for v1.1.0 of the app has begun.

Getting Started

Your team will have both roles of Developers and Maintainers for all the people in the team. As Maintainers, you will be responsible for cutting new releases and accepting Pull Requests from other team members. As Maintainers you should have write access to this repository and as Developers should have read access in the other teammate repositories.

Project Structure

• Application code can be found in the /app/ folder.
• The application contains a file named VERSION that contains the major, minor, and patch numbers for the project.
• Source files are written in markdown and can be identified by the .md file extension.

Next

Next, we will walk through the process of creating a GitHub Fork and the local clone of this repository.

Go

Quick Links

• 1. Setup
• 2. Feature Branches
• 3. Code Review
• 4. Fetching the Latest
• 5. Hotfix
• 6. Release Branch
• 7. Release Bugs
• 8. Completed Release