You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thu 5/28/2026: my private learning still has zero issues and now challenges.md in its docs directory. Looks like the bot did not run or aborted when it tried.
Hi Debee, thank you for your patience - and our sincere apology. A fault in our provisioning system on our side meant your private learning room was not created when you enrolled. That fault is fixed, monitored, and will not affect you again.
Your learning room now exists and an invitation is on its way to you:
Check your email for a message from GitHub with "invitation" in the subject, or open your GitHub notifications (the notification bell, or https://github.com/notifications).
Activate the View invitation link, then the Accept invitation button.
If you cannot find the invitation email, open your repository link above while signed in to GitHub - the invitation banner with the Accept button appears at the top of the page.
GitHub invitations expire after seven days. If yours has expired or anything does not work, reply here or open a support issue and we will send a fresh one the same day: https://github.com/Community-Access/support/issues
What to do first
Accept the invitation and open your learning room repository.
Read the README - it orients you to how the room works.
Open the Issues tab and start with Challenge 1. Every challenge has instructions, an "If You Get Stuck" section, and a worked reference solution.
I accepted the invitation, all good.
I read the readme, same readme as before.
I found the challenges.md in the docs directory, it seemed complete.
However there are still zero issues.
On the Actions tab and under Workflow runs it shows zero ran.
"There are no workflow runs yet." is displayed.
So I think a bot needs to still run to populate the issues so I can publish evidence that I’ve completed each challenge.
If my understanding is incorrect, please let me know.
A message does read that I can now "push" to this learning room repo. So I can do its challenges from the challenges.md document and from the descriptions in the workshop docs, but I cannot use issues as a guide to publish my evidence, as they do not yet exist.
Hi Debbie, thank you for the clear report - you were right, and it is fixed.
The fault was on our side: provisioning created your learning room and gave you push access, but the step that opens your first challenge issue never ran. We have corrected that in the provisioning system itself, so it will not happen to you or anyone else again.
Your first challenge is waiting for you now, assigned to you:
Each challenge issue contains the full instructions and an "If You Get Stuck" section. When you finish a challenge, add your evidence as a comment and close the issue - Gandalf will open the next one automatically.
I am closing this enrollment issue now that everything is in place. If anything else does not behave, reply here or open a support issue and we will jump on it: https://github.com/Community-Access/support/issues
Activity
github-actions commentedon May 27, 2026
You are enrolled. Welcome!
Hi Debee Armstrong, great job submitting your first step.
Next steps
Day 2 content automatically unlocks in your learning room after you complete Day 1 challenges.
Where to see replies
Please reply
ackon this issue after you confirm your Day 1 link works.Then close this enrollment issue as Challenge 0.
If you get stuck at any step, open support:
You belong here.
DebeeArmstrong commentedon May 29, 2026
Thu 5/28/2026: my private learning still has zero issues and now challenges.md in its docs directory. Looks like the bot did not run or aborted when it tried.
accesswatch commentedon Jul 2, 2026
Your learning room is ready
Hi Debee, thank you for your patience - and our sincere apology. A fault in our provisioning system on our side meant your private learning room was not created when you enrolled. That fault is fixed, monitored, and will not affect you again.
Your learning room now exists and an invitation is on its way to you:
Your repository: https://github.com/Community-Access/learning-room-self-paced-2026-debeearmstrong
How to accept your invitation
GitHub invitations expire after seven days. If yours has expired or anything does not work, reply here or open a support issue and we will send a fresh one the same day: https://github.com/Community-Access/support/issues
What to do first
When your invitation works, please reply
ackon this issue so we know you are in.You enrolled, you waited longer than you ever should have, and you are exactly who this workshop is for. You belong here.
-- The Community Access facilitation team
DebeeArmstrong commentedon Jul 2, 2026
DebeeArmstrong commentedon Jul 2, 2026
A message does read that I can now "push" to this learning room repo. So I can do its challenges from the challenges.md document and from the descriptions in the workshop docs, but I cannot use issues as a guide to publish my evidence, as they do not yet exist.
fix(provisioning): seed Challenge 1 at provision time and tolerate pe…
accesswatch commentedon Jul 3, 2026
Your challenges are ready
Hi Debbie, thank you for the clear report - you were right, and it is fixed.
The fault was on our side: provisioning created your learning room and gave you push access, but the step that opens your first challenge issue never ran. We have corrected that in the provisioning system itself, so it will not happen to you or anyone else again.
Your first challenge is waiting for you now, assigned to you:
Challenge 1: Find Your Way Around: https://github.com/Community-Access/learning-room-self-paced-2026-debeearmstrong/issues/1
Each challenge issue contains the full instructions and an "If You Get Stuck" section. When you finish a challenge, add your evidence as a comment and close the issue - Gandalf will open the next one automatically.
I am closing this enrollment issue now that everything is in place. If anything else does not behave, reply here or open a support issue and we will jump on it: https://github.com/Community-Access/support/issues
Thank you for your patience. You belong here.
-- The Community Access facilitation team