Skip to content

Commit c879b76

Browse files
committed
docs: remove 'Allow Actions' setup step, renumber steps
The workflow-permissions toggle was only needed for the Set Up Blog workflow (now removed). Steps 4 and 5 become steps 3 and 4.
1 parent 6b90b6c commit c879b76

1 file changed

Lines changed: 2 additions & 8 deletions

File tree

README.md

Lines changed: 2 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -56,13 +56,7 @@ Click **[Fork](https://docs.github.com/en/get-started/quickstart/fork-a-repo)**
5656

5757
Go to [**Settings → Pages → Build and deployment**](../../settings/pages) and set the source to **GitHub Actions**.
5858

59-
### 3. Allow Actions to manage repository settings
60-
61-
Go to [**Settings → Actions → General → Workflow permissions**](../../settings/actions) and select **Read and write permissions**, then click **Save**.
62-
63-
This one-time toggle lets the built-in GITHUB_TOKEN create repository variables when you run the **Set Up Blog** workflow — no personal access token or extra credentials needed. The build workflow itself only needs read access; this setting is required only for the setup step.
64-
65-
### 4. Configure your blog (optional)
59+
### 3. Configure your blog (optional)
6660

6761
Connect optional content sources — no code or API keys needed:
6862

@@ -75,7 +69,7 @@ The **[Set Up Blog](../../actions/workflows/setup-blog.yml)** workflow saves you
7569

7670
> **Tip:** You can skip this step entirely and come back later — the blog works out of the box with just GitHub Issues.
7771
78-
### 5. Publish your first post
72+
### 4. Publish your first post
7973

8074
1. [Open a new Issue](../../issues/new) in your forked repository.
8175
2. Give it a descriptive **title** — this becomes your post title.

0 commit comments

Comments
 (0)