[workshop-sim] Repair: Front-load Copilot access/billing pre-check in Step 7
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 77/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github, github-actions
- Domain
- documentation
Research direction
Start with 07-your-first-workflow.md and read the existing billing-path explanation in side-quest-07d-billing-paths.md. Add an early callout before “Create your first workflow” that links to github.com/settings/copilot and asks whether centralized Copilot billing for GitHub Actions is enabled for the repository. Keep the existing checks and activities, then confirm the shared assessment scores and learning KPI do not decrease.
Written by the indexing model from the issue text.
Description
Problem statement
Step 07-first-workflow (mapped to 07-your-first-workflow.md + 07d-confirm-model-access.md) is now the single highest-dropout step in the workshop at 21.4% conditional dropout (4,892 of 22,842 at-risk simulated runs), dominated by the copilot-access-missing failure category (4,109 of those failures). Learners reach the model-access verification prompt (gh copilot / /agentic-workflows ...) before they discover whether their account actually has usable Copilot access or an active centralized-billing arrangement — so the cost of discovering the blocker is paid only after they have already started authoring the workflow file.
Proposed change
Add an earlier, lightweight Copilot-access/billing pre-check at the very top of 07-your-first-workflow.md (before "Create your first workflow"), pointing directly to github.com/settings/copilot and the billing-path decision ("Is centralized Copilot billing for GitHub Actions enabled for this repository?") that currently only appears later, inside side-quest-07d-billing-paths.md. Keep the existing in-page checks intact; this is additive front-loading, not a replacement.
Failure mode classification
Access barrier (account entitlement / billing configuration, not a conceptual or scaffolding gap).
Quantitative guardrail
Current scores for 07-your-first-workflow.md:
overall_score: 6.25/10- Weakest rubric dimension:
checkpoint_quality(0.0/10) - Learning KPI index: 3.65/10 (
active_learning6.3,checkpoint_quality0.0,scaffolding5.0)
This change only adds an early pre-check callout; it does not touch the existing activity density, checklist items, or prerequisite section, so active_learning, scaffolding, and checkpoint_quality — and therefore overall_score and the learning KPI index — should stay flat or improve as a side effect of any later checkpoint-detection fix, never decrease.
Acceptance criteria
- The shared curriculum quantitative assessment
overall_scorefor07-your-first-workflow.mdstays flat or improves after the change - The step's learning KPI index (
(2.0 × active_learning + 2.0 × checkpoint_quality + 1.5 × scaffolding) / 5.5) stays flat or improves - Hands-on practice, checkpoints, and scaffolding (the existing Copilot CLI test-prompt activity and checklist) are preserved or strengthened, not removed or weakened
- The new pre-check callout links to both
github.com/settings/copilotand the billing-path decision question, and appears before the "Create your first workflow" section
Suggested owner
workshop maintainer
Related to #4493
Generated by 🔬 Workshop Student Simulator · copilot · auto · 309.7 AIC · ⌖ 14.8 AIC · ⊞ 15.1K · ◷
- expires on Oct 13, 2026, 8:28 AM UTC
- Dominant language
- JavaScript
- Stars
- 52
- Forks
- 26
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 15
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
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 88/100
githubnext/gh-aw-workshop#4496 ·
Maintainers usually reply within 1 day
-
feedback simulation workshop
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
githubnext/gh-aw-workshop#4495 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
githubnext/gh-aw-workshop#4491 ·
Maintainers usually reply within 1 day
-
[workshop-sync] workshop/06-install-gh-aw.md: inaccurate gh aw init output and stale version exampleOpendocumentation
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-workshop#4490 ·
Maintainers usually reply within 1 day
-
curriculum documentation quality
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
githubnext/gh-aw-workshop#4488 ·
Maintainers usually reply within 1 day
All issues in githubnext/gh-aw-workshop
Similar issues
-
Language MVP task
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
saayam-for-all/webapp#1914 ·
Maintainers usually reply within 1 day
-
[Bug] Dev image build fails: `npm install` in the root Dockerfile runs out of memory (exit 134)Possibly taken @andest01 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
good first issue hacktoberfest help wanted
Difficulty 2/5 Under an hour Newbie friendliness 76/100
pacocartones/free-llm-api-hub#262 ·
Maintainers usually reply within 1 day
-
agent-task risk:low
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
guyellis/http-status-check#512 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoft/playwright#43327 ·
Maintainers usually reply within 1 day