[workshop-sync] workshop/side-quest-16-02-secrets-and-permissions.md: "GitHub Secrets" link points to Safe Outputs page
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, markdown
- Domain
- documentation
Research direction
Open workshop/side-quest-16-02-secrets-and-permissions.md and check the “GitHub Secrets” link on line 14. Replace its target with the GitHub Actions secrets documentation URL given in the issue, then verify the link points there; the issue also permits removing the link. Done when the misleading Safe Outputs target is no longer used for “GitHub Secrets.”
Written by the indexing model from the issue text.
Description
Workshop file reviewed
workshop/side-quest-16-02-secrets-and-permissions.md
Problem
Line 14 links the text "GitHub Secrets" to the gh-aw Safe Outputs reference, which doesn't cover repository secrets:
**[GitHub Secrets](https://github.github.com/gh-aw/reference/safe-outputs/)**
Correct target
Secrets are a GitHub Actions feature, so link to GitHub's own docs: https://docs.github.com/en/actions/security-for-github-actions/security-guides/using-secrets-in-github-actions (the gh-aw safe-outputs page is about validated write operations).
Suggested fix
Replace the URL on line 14 with the GitHub Docs secrets URL above, or remove the link.
Context: reviewed with gh-aw v0.92.0 (no new release since the last check). The other two files in this batch, side-quest-16-01 and side-quest-16-03, had no issues.
Generated by 🔍 Workshop Sync Check · copilot · auto · 51.7 AIC · ⌖ 0.551 AIC · ⊞ 9.2K · ◷
- expires on Oct 17, 2026, 11:32 PM UTC
- Dominant language
- JavaScript
- Stars
- 53
- Forks
- 35
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 15
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from githubnext/gh-aw-workshop
-
[workshop-sim] Improve: Add verifiable checkpoint and bridge to Step 5 (What Are Agentic Workflows?)Openfeedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
githubnext/gh-aw-workshop#4715 ·
Maintainers usually reply within 1 day
-
[curriculum-eval] 05-agentic-workflows-intro.md: cognitive_load — 1,107 words with three activitiesOpencurriculum documentation quality
Difficulty 1/5 1-3 hours Newbie friendliness 94/100
githubnext/gh-aw-workshop#4706 ·
Maintainers usually reply within 1 day
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
githubnext/gh-aw-workshop#4705 ·
Maintainers usually reply within 1 day
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-workshop#4703 ·
Maintainers usually reply within 1 day
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
githubnext/gh-aw-workshop#4704 ·
Maintainers usually reply within 1 day
All issues in githubnext/gh-aw-workshop
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
521xueweihan/HelloGitHub#4025 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
yetone/magpie#2844 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
c1overzz/dsh-bili-scroll#22 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
maproulette/maproulette-frontend#2944 ·
Maintainers usually reply within 1 day