You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Go to [**Settings → Pages → Build and deployment**](../../settings/pages) and set the source to **GitHub Actions**.
58
58
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)
66
60
67
61
Connect optional content sources — no code or API keys needed:
68
62
@@ -75,7 +69,7 @@ The **[Set Up Blog](../../actions/workflows/setup-blog.yml)** workflow saves you
75
69
76
70
> **Tip:** You can skip this step entirely and come back later — the blog works out of the box with just GitHub Issues.
77
71
78
-
### 5. Publish your first post
72
+
### 4. Publish your first post
79
73
80
74
1.[Open a new Issue](../../issues/new) in your forked repository.
81
75
2. Give it a descriptive **title** — this becomes your post title.
0 commit comments