[workshop-sync] side-quest-16-02-secrets-and-permissions.md: "GitHub Secrets" link points to safe-outputs page
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 85/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github, markdown
- Domain
- documentation
Research direction
Open workshop/side-quest-16-02-secrets-and-permissions.md and check the “GitHub Secrets” link. Point it to the GitHub Actions secrets documentation URL suggested in the issue, or remove the link. Done when the link text and destination are accurate; review the resulting Markdown change.
Written by the indexing model from the issue text.
Description
Workshop file reviewed
workshop/side-quest-16-02-secrets-and-permissions.md
Problem
The link text and target don't match:
**[GitHub Secrets](https://github.github.com/gh-aw/reference/safe-outputs/)**
The target is the gh-aw Safe Outputs reference, which doesn't cover storing or managing repository secrets.
Suggested fix
Link to GitHub's secrets docs (https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions) or drop the link.
Reviewed alongside side-quest-15-02-chaining-conditions.md and side-quest-16-01-github-output.md (no issues). gh-aw release: v1.0.1.
Generated by 🔍 Workshop Sync Check · copilot · auto · ~53 AIC · ⌖ ~1 AIC · ⊞ 4.7K · ◷
- expires on Nov 7, 2026, 4:06 PM UTC
- Dominant language
- JavaScript
- Stars
- 58
- Forks
- 40
- Avg merge
- 4d 4h
- Merged PRs (30d)
- 8
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
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
githubnext/gh-aw-workshop#5437 ·
Maintainers usually reply within 3 days
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
githubnext/gh-aw-workshop#5436 ·
Maintainers usually reply within 3 days
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
githubnext/gh-aw-workshop#5434 ·
Maintainers usually reply within 3 days
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
githubnext/gh-aw-workshop#5433 ·
Maintainers usually reply within 3 days
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
githubnext/gh-aw-workshop#5427 ·
Maintainers usually reply within 3 days
All issues in githubnext/gh-aw-workshop
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
microsoft/monaco-editor#5575 ·
Maintainers usually reply within 1 day
-
stringify escapes leading digits in pseudo-class arguments (:nth-child(1) becomes :nth-child(\31 ))Open
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
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
digitalbazaar/forge#1170 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days