https://github.com/tcarters/skills-release-based-workflow
My clone repository
https://github.com/tcarters/skills-release-based-workflow
Last synced: over 1 year ago
JSON representation
My clone repository
- Host: GitHub
- URL: https://github.com/tcarters/skills-release-based-workflow
- Owner: Tcarters
- License: mit
- Created: 2023-06-16T23:08:27.000Z (about 3 years ago)
- Default Branch: main
- Last Pushed: 2023-10-01T21:22:08.000Z (almost 3 years ago)
- Last Synced: 2025-01-23T02:44:44.925Z (over 1 year ago)
- Language: JavaScript
- Size: 86.9 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Create a release based workflow
_Create a release based workflow that is built on the foundations of the GitHub flow._
## Step 2: Add a new feature to the release branch
_Great job creating a beta release :heart:_
### Release management
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.
### Protected branches
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.
### Add a feature
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.
### :keyboard: Activity: Update `base.css`
1. Create a new branch off of the `main` branch and change the `body` CSS declaration in `base.css` to match what is below. This will set the page background to black.
```
body {
background-color: black;
}
```
1. Open a pull request with `release-v1.0` as the `base` branch, and your new branch as the `compare` branch.
1. Fill in the pull request template to describe your changes.
1. Click **Create pull request**.
### Merge the new feature to the release branch
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.
### :keyboard: Activity: Merge the pull request
1. Click **Merge pull request**, and delete your branch.
1. Wait about 20 seconds then refresh this page (the one you're following instructions from). [GitHub Actions](https://docs.github.com/en/actions) will automatically update to the next step.
---
Get help: [Post in our discussion board](https://github.com/skills/.github/discussions) • [Review the GitHub status page](https://www.githubstatus.com/)
© 2023 GitHub • [Code of Conduct](https://www.contributor-covenant.org/version/2/1/code_of_conduct/code_of_conduct.md) • [MIT License](https://gh.io/mit)