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

[guidelines] side-quest-07d-billing-paths.md: missing page annotation lines

Closed Beginner friendly
#3,631 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
95/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
markdown
Domain
documentation

Research direction

Open workshop/side-quest-07d-billing-paths.md and compare its opening with the Workshop page annotation schema. Verify the file currently begins with the heading, then add the required annotation comments before it. Done means the file starts with both page-journey and page-adventure lines and remains valid workshop content.

Written by the indexing model from the issue text.

Description

documentation guidelines

File reviewed

workshop/side-quest-07d-billing-paths.md

Violations

Missing workshop page annotation lines

Offending text:

(file starts directly with # Side Quest: Copilot Billing Paths — no annotation comments precede it)

Suggested fix:
Add <!-- page-journey: all --> and <!-- page-adventure: side-quest --> as the first two lines of the file, before the # heading, per the "Workshop page annotation schema" rule. Every workshop file except README.md must start with these two XML comment lines so tooling can filter pages by learner profile; this file is currently the only one in the round-robin batch missing them.

Generated by 📋 Guidelines Enforcer · copilot · auto · 115.2 AIC · ⌖ 6.37 AIC · ⊞ 9.1K · ◷

  • expires on Sep 28, 2026, 4:04 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.