Create a release based workflow

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

Step 3: Open a release pull request

Nice work adding a new feature 😄

Release branches and `main`

You should open a pull request between your release branch and main as early as possible. It might be open for a long time, and that's okay.

In general, the pull request description can include:

A reference to an issue that the pull request addresses.
A description of the changes proposed in the pull request.
@mentions of the person or team responsible for reviewing proposed changes.

To expedite the creation of this pull request, I've added a pull request template to the repository. When you create a pull request, default text will automatically be displayed. This should help you identify and fill out all the necessary information. If you don't want to use the template content, just remove the text from the pull request and repace it with your pull request message.

⌨️ Activity: Open a release pull request

Let's make a new pull request comparing the release-v1.0 branch to the main branch.

Open a new pull request with base: main and compare: release-v1.0.
Ensure the title of your pull request is "Release v1.0".

Include a detailed pull request body, an example is below:

## Description:
- Changed page background color to black.
- Changed game text color to green.

Click Create pull request.
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

About

Microsoft dev challenge #11

MIT License

Languages