Create a release based workflow

Create a release based workflow that is built on the foundations of the GitHub flow.

Step 1: Create a beta release

Welcome to "Release-based workflow" ❇️

The GitHub flow

The GitHub flow is a lightweight, branch-based workflow for projects with regular deployments.

Some projects may deploy more often, with continuous deployment. There might be a "release" every time there's a new commit on main.

But, some projects rely on a different structure for versions and releases.

Versions

Versions are different iterations of updated software like operating systems, apps, or dependencies. Common examples are "Windows 8.1" to "Windows 10", or "macOS High Sierra" to "macOS Mojave".

Developers update code and then run tests on the project for bugs. During that time, the developers might set up certain securities to protect from new code or bugs. Then, the tested code is ready for production. Teams version the code and release it for installation by end users.

⌨️ Activity: Create a release for the current codebase

In this step, you will create a release for this repository on GitHub.

GitHub Releases point to a specific commit. Releases can include release notes in Markdown files, and attached binaries.

Before using a release based workflow for a larger release, let's create a tag and a release.

Open a new browser tab, and work on the steps in your second tab while you read the instructions in this tab.
Go to the Releases page for this repository.
- Tip: To reach this page, click the Code tab at the top of your repository. Then, find the navigation bar below the repository description, and click the Releases heading link.
Click Create a new release.
In the field for Tag version, specify a number. In this case, use v0.9. Keep the Target as main.
Give the release a title, like "First beta release". If you'd like, you could also give the release a short description.
Select the checkbox next to Set as a pre-release, since it is representing a beta version.
Click Publish release.

⌨️ Activity: Introduce a bug to be fixed later

To set the stage for later, let's also add a bug that we'll fix as part of the release workflow in later steps. We've already created a update-text-colors branch for you so let's create and merge a pull request with this branch.

Open a new pull request with base: release-v1.0 and compare: update-text-colors.
Set the pull request title to "Updated game text style". You can include a detailed pull request body, an example is below:
```
## Description:
- Updated game text color to green
```
Click Create pull request.
We'll merge this pull request now. 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.