An exercise for learning the Trunk-based development model. This exercise will walk your team through adding features to an example application.
Read the instructions for each stage carefully. If you're not sure what the instructions mean stop and take time to understand them. If you rush into running Git commands you'll make mistakes and they can be difficult to undo.
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.
Your team is made up of two or three developers. Each of you will contribute new content to the project from your computers and also review other developers contributions.
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.
- Application code can be found in the
/app/folder. - Source files are written in markdown and can be identified by the
.mdfile extension.
Next we will walk through the process of creating a GitHub Fork and local clone of this repository.