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

[workflow-editor] Remove duplicate golden-ticket billing guidance from guidelines.md

Closed Beginner friendly
  • Is something wrong?
#4,139 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
82/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
github-actions
Domain
documentation

Research direction

Edit .github/workflows/guidelines.md, comparing the detailed golden-ticket statement under "Workshop delivery assumptions" with the duplicate under "Golden-Ticket Workshop Surfaces." Keep the detailed rule and replace the repetition with a one-line reference, then validate the seven dependent workflows with --validate and confirm no lock file content changes.

Written by the indexing model from the issue text.

Description

agentic-workflows documentation workflow-editor

[!CAUTION]
Protected files were modified in this change.
This pull request is in request_review mode and requires explicit human scrutiny before merge.

Protected files: .github/workflows/guidelines.md

What changed

.github/workflows/guidelines.md stated the golden-ticket org/billing provisioning rule twice, nearly verbatim:

  • "Workshop delivery assumptions" → Org and billing are pre-provisioned.
  • "Golden-Ticket Workshop Surfaces" → Org provisioning and billing are handled by the golden-ticket system.

Both bullets said the provisioning tooling creates the workshop org, assigns Copilot seats, and covers billing, and that core workshop content should not include org/billing setup steps. Keeping both forces every workflow that imports this shared guidelines file to re-read the same instruction twice.

Fix

Kept the detailed statement in "Workshop delivery assumptions" (the first and more complete occurrence) and shortened the "Golden-Ticket Workshop Surfaces" bullet to a one-line summary that points back to it, instead of repeating the full rule.

File changed

  • .github/workflows/guidelines.md (one bullet shortened, no behavior change)

Why this is more Skills-like

GitHub Skills lessons state a rule once and reference it, rather than restating full guidance in multiple sections. This keeps the shared guidelines file leaner for every dependent workflow (guidelines-enforcer, side-quest, security-side-quest, workshop-author, workshop-explanatory-diagrams, workshop-skill-activity-author, workshop-ui-screenshots) that reads it, without losing any guidance — the full rule is still stated once, just not twice.

No lock files needed regeneration: guidelines.md is referenced by path (not inlined) in the dependent workflows, so I validated by recompiling all seven dependent workflows with --validate and confirmed no lock file content changed as a result of this edit.

[!WARNING]

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

  • registry.npmjs.org

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "registry.npmjs.org"

See Network Configuration for more information.

Generated by ✂️ Workflow Skills Editor · copilot · auto · 54.7 AIC · ⌖ 8.2 AIC · ⊞ 9.5K · ◷

  • expires on Oct 4, 2026, 7:42 AM UTC

[!NOTE]
This was originally intended as a pull request, but the git push operation failed.

Original error: The process '/usr/bin/git' failed with exit code 1

Workflow Run: View run details and download bundle artifact

The bundle file is available in the agent artifact in the workflow run linked above.

Create the pull request manually 
# Download the artifact from the workflow run
gh run download '37106933547' -n agent -D '/tmp/agent-37106933547'

# Resolve the bundle source ref, fetch it into a temporary ref, then create the local branch
bundle_path='/tmp/agent-37106933547/aw-workflow-editor-dedup-golden-ticket-guidelines.bundle'
temp_ref='refs/bundles/create-pr-workflow-editor-dedup-golden-ticket-guidelines-4f616f84ace678f0-9ac95883'
target_ref='refs/heads/workflow-editor/dedup-golden-ticket-guidelines-4f616f84ace678f0'
bundle_source_ref=$(git bundle list-heads "$bundle_path" | awk '$2 ~ /^refs\/heads\// { print $2 }')
if [ -z "$bundle_source_ref" ]; then
  bundle_source_ref=$(git bundle list-heads "$bundle_path" | awk '$2 == "HEAD" { print $2 }')
fi
if [ "$(printf '%s\n' "$bundle_source_ref" | sed '/^$/d' | wc -l | tr -d ' ')" != "1" ]; then
  echo "Expected exactly one bundle source ref, found: $bundle_source_ref" >&2
  exit 1
fi
git fetch "$bundle_path" "${bundle_source_ref}:${temp_ref}"
git update-ref "$target_ref" "$temp_ref"
git checkout 'workflow-editor/dedup-golden-ticket-guidelines-4f616f84ace678f0'
# Ensure the working tree matches the updated branch
git reset --hard
# Remove the temporary bundle ref
git update-ref -d "$temp_ref"

# Push the branch to the target remote
git push 'origin' 'workflow-editor/dedup-golden-ticket-guidelines-4f616f84ace678f0'

# Create the pull request
gh pr create --title '[workflow-editor] Remove duplicate golden-ticket billing guidance from guidelines.md' --base 'main' --head 'workflow-editor/dedup-golden-ticket-guidelines-4f616f84ace678f0' --repo 'githubnext/gh-aw-workshop'
Dominant language
JavaScript
Stars
51
Forks
23
Avg merge
11h 32m
Merged PRs (30d)
22

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.