Skip to content

Commit a18f270

Browse files
authored
fix: remove numbered prefixes from section headers in 11a-build-daily-status-terminal.md (#1594)
1 parent 311610c commit a18f270

1 file changed

Lines changed: 7 additions & 7 deletions

File tree

workshop/11a-build-daily-status-terminal.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ New to workflow file structure? See [Workflow File Structure at a Glance](side-q
4848

4949
---
5050

51-
## Section 1 — Metadata
51+
## Metadata
5252

5353
Start with the opening fence and the two metadata keys. `emoji` is the visual label shown in `gh aw list`; `description` is the one-sentence summary displayed in the GitHub Actions UI.
5454

@@ -62,7 +62,7 @@ description: Post a daily repository status summary as a GitHub issue comment.
6262
6363
---
6464
65-
## Section 2 — Triggers
65+
## Triggers
6666
6767
Add the trigger block after the `description` line. `schedule: daily` is `gh-aw`'s shorthand that compiles to a once-per-day cron schedule. The compiler automatically adds a **Run workflow** button for any scheduled workflow; you may include `workflow_dispatch: {}` explicitly here for clarity, but it is not required.
6868

@@ -76,9 +76,9 @@ on:
7676

7777
---
7878

79-
## Section 3 — Permissions
79+
## Permissions
8080

81-
Add the minimum permissions the workflow needs. `copilot-requests: write` is required by every agentic workflow; the remaining entries are read-only. Write access for issue comments is declared via `safe-outputs` in Section 5.
81+
Add the minimum permissions the workflow needs. `copilot-requests: write` is required by every agentic workflow; the remaining entries are read-only. Write access for issue comments is declared via `safe-outputs` in the [Write guardrail](#write-guardrail) section.
8282

8383
```yaml
8484
permissions:
@@ -93,7 +93,7 @@ permissions:
9393

9494
---
9595

96-
## Section 4 — Tools
96+
## Tools
9797

9898
The `tools` block enables GitHub API access. `mode: gh-proxy` routes all API calls through a controlled proxy that enforces only the scopes declared in `permissions` above (see [Side Quest: Tools, Outputs, and the Agent Body](side-quest-11-08-frontmatter-tools-outputs.md) for details).
9999

@@ -108,7 +108,7 @@ tools:
108108

109109
---
110110

111-
## Section 5 — Write guardrail
111+
## Write guardrail
112112

113113
`safe-outputs` declares the only write action allowed: one issue comment per run. Any other write actions the agent attempts are blocked.
114114

@@ -123,7 +123,7 @@ safe-outputs:
123123

124124
---
125125

126-
## Section 6 — Agent instructions
126+
## Agent instructions
127127

128128
Add the Markdown body **below** the closing `---`. This is the brief the AI agent reads and follows at runtime.
129129

0 commit comments

Comments
 (0)