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

[workshop-sync] workshop/side-quest-06-03a-copilot-requests-permission.md: missing `features: copilot-requests: true` flag

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions
Domain
documentation

Research direction

Start with the frontmatter example in workshop/side-quest-06-03a-copilot-requests-permission.md, then check the features: flags in the gh-aw syntax-agentic.md reference and the special-permission-copilot-requests-write anchor in the permissions reference to confirm whether copilot-requests: true is required. Done when the frontmatter example, the "single line" claim, the troubleshooting row, the numbered checks and the checkpoint all name both settings consistently, and the sibling side-quest files stay unchanged.

Written by the indexing model from the issue text.

Description

documentation

Workshop file reviewed

workshop/side-quest-06-03a-copilot-requests-permission.md (gh-aw v0.89.21)

Problem

The page presents a single permission line as the only change needed:

That single line is the only workflow authentication change required for repositories that can use Method 1.

The frontmatter example only adds copilot-requests: write under permissions.

Current correct syntax

The gh-aw reference (syntax-agentic.md, features: known flags) says copilot-requests: true means "Use GitHub Actions token for Copilot authentication instead of COPILOT_GITHUB_TOKEN secret". In syntax-core.md, copilot-requests: write is listed only as a recommended permission scope.

Suggested fix

Add to the frontmatter example:

features:
  copilot-requests: true
permissions:
  contents: read
  copilot-requests: write

Then update the "single line" claim, the troubleshooting table row for missing frontmatter, the numbered checks, and the checkpoint to mention both. Please verify against the current docs before editing, since the permissions reference has a special-permission-copilot-requests-write anchor and the exact requirement may vary.

Other files reviewed this run (side-quest-06-03-copilot-token.md and side-quest-06-03b-copilot-github-token.md) had no issues.

Generated by 🔍 Workshop Sync Check · copilot · auto · 47.1 AIC · ⌖ 0.545 AIC · ⊞ 9.2K · ◷

  • expires on Oct 15, 2026, 11:38 AM UTC
Dominant language
JavaScript
Stars
53
Forks
35
Avg merge
13h 50m
Merged PRs (30d)
14

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.