Skip to content

Commit b2efa4f

Browse files
author
github-actions
committed
Update to 1 in STEP and README.md
1 parent 6daa9c1 commit b2efa4f

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

.github/script/STEP

+1-1
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
0
1+
1

README.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77

88
# Create a release based workflow
99

10-
<!--step0-->
10+
<!--step0
1111
Create a release based workflow that is built on the foundations of the [GitHub flow](https://guides.github.com/introduction/flow/). When your team uses a release-based workflow, GitHub makes it easy to collaborate with deployable iterations of your project that you can package and make available for a wider audience to download and use.
1212
1313
GitHub releases allow your team to package and provide software to your users based on a specific point in the history of your project.
@@ -27,10 +27,10 @@ GitHub releases allow your team to package and provide software to your users ba
2727
- We recommend creating a public repository-private repositories will [use Actions minutes](https://docs.github.com/en/billing/managing-billing-for-github-actions/about-billing-for-github-actions).
2828
![Create a new repository](https://user-images.githubusercontent.com/1221423/169618722-406dc508-add4-4074-83f0-c7a7ad87f6f3.png)
2929
3. After your new repository is created, wait about 20 seconds, then refresh the page. Follow the step-by-step instructions in the new repository's README.
30-
<!--endstep0-->
30+
endstep0-->
3131

3232
<!--Step 1-->
33-
<details id=1>
33+
<details id=1 open>
3434
<summary><h2>Step 1: Create a beta release</h2></summary>
3535

3636
### The GitHub flow

0 commit comments

Comments
 (0)