Create a release based workflow that is built on the foundations of the GitHub flow.
Great job creating a beta release ❤️
As you prepare for a future release, you'll need to organize more than the tasks and features. It's important to create a clear workflow for your team, and to make sure that the work remains organized.
There are several strategies for managing releases. Some teams might use long-lived branches, like production
, dev
, and main
. Some teams use simple feature branches, releasing from the main branch.
No one strategy is better than another. We always recommend being intentional about branches and reducing long-lived branches whenever possible.
In this exercise, you'll use the release-v1.0
branch to be your one long-lived branch per release version.
Like the main
branch, you can protect release branches. This means you can protect branches from force pushes or accidental deletion. This is already configured in this repository.
Releases are usually made of many smaller changes. Let's pretend we don't know about the bug we added earlier and we'll focus on a few features to update our game before the version update.
- You should update the page background color to black.
- I'll help you change the text colors to green.
- Create a new branch off of the
main
branch and change thebody
CSS declaration inbase.css
to match what is below. This will set the page background to black.
body {
background-color: black;
}
- Open a pull request with
release-v1.0
as thebase
branch, and your new branch as thecompare
branch. - Fill in the pull request template to describe your changes.
- Click Create pull request.
Even with releases, the GitHub flow is still an important strategy for working with your team. It's a good idea to use short-lived branches for quick feature additions and bug fixes.
Merge this feature pull request so that you can open the release pull request as early as possible.
- Click Merge pull request, and delete your branch.
- Wait about 20 seconds then refresh this page (the one you're following instructions from). GitHub Actions will automatically update to the next step.
Get help: Post in our discussion board • Review the GitHub status page
© 2023 GitHub • Code of Conduct • MIT License