Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[workshop-sync] workshop/side-quest-16-02-secrets-and-permissions.md: "GitHub Secrets" link points to safe-outputs docs instead of secrets docs

Closed Beginner friendly
  • Is something wrong?
#4,413 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
78/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions
Domain
documentation

Research direction

The wrong link is in the intro paragraph of workshop/side-quest-16-02-secrets-and-permissions.md, on the phrase "GitHub Secrets". Compare it with the gh-aw safe-outputs reference, which covers a different feature, and check the secrets documentation the issue points to. Done when the "GitHub Secrets" link goes to a page that describes secrets and the rest of the paragraph still reads correctly.

Written by the indexing model from the issue text.

Description

documentation

Workshop file reviewed

workshop/side-quest-16-02-secrets-and-permissions.md

Problem

The intro paragraph links the phrase "GitHub Secrets" to the gh-aw safe-outputs reference page, which is unrelated:

GitHub Secrets gives you a secure vault for sensitive values that workflows can read without exposing.

The linked URL (reference/safe-outputs/) documents gh-aw's safe-outputs: frontmatter key (e.g. create-issue, add-comment) — a feature for controlling what write operations an agent can perform. It has no connection to GitHub Secrets or credential storage.

Current correct reference

gh-aw's own frontmatter reference documents a dedicated secrets: field (see syntax-core.md in the gh-aw docs, "secrets: - Secret values passed to workflow execution"), which is topically appropriate here. Alternatively, since this concept is really about GitHub Actions' built-in encrypted-secrets feature rather than a gh-aw-specific mechanism, the link could point to GitHub's own Actions secrets documentation (docs.github.com/actions/security-guides/using-secrets-in-github-actions) instead of an unrelated gh-aw reference page.

Suggested fix

Update the link target for "GitHub Secrets" in the intro paragraph to point to either:

  • GitHub's official Actions secrets documentation, or
  • gh-aw's secrets: frontmatter reference (if a published docs anchor exists for it)

instead of https://github.github.com/gh-aw/reference/safe-outputs/.

Generated by 🔍 Workshop Sync Check · copilot · auto · 119.2 AIC · ⌖ 6.19 AIC · ⊞ 9.2K · ◷

  • expires on Oct 11, 2026, 6:59 AM UTC
Dominant language
JavaScript
Stars
52
Forks
26
Avg merge
12h 58m
Merged PRs (30d)
15

Getting set up

Open in Codespaces

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from githubnext/gh-aw-workshop

All issues in githubnext/gh-aw-workshop

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.