Repository navigation
docs(troubleshooting): explain disabled Commit and Push in github.dev after room updates - #244
Conversation
… after room updates A learner with confirmed write access hit a disabled Commit and Push in github.dev because the editor's copy of her Learning Room went stale after maintenance commits were pushed to the room (Community-Access/support#59). Copilot then misreported it as a permissions problem. - Add a Common Issues entry to Appendix J with reload-and-recover steps - Add a matching troubleshooting row to the Challenge 5 issue template - Regenerate html/ and work.md Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Learning Room Validation ReportGreat work. Your changes look good. Resources |
|
Hi! I am Gandalf, your workshop agent. I bring a little magic to make this interaction clear, helpful, and fun. Here is my review of your pull request: Report StatusValidation Needs Attention [ACTION REQUIRED] Required Checks
Learning ResourcesBased on your changes, these guides might help: Automated validation by Learning Room Bot. Gandalf generated this review. Last updated: 2026-07-04T19:59:27.048Z |
github-actions
Bot
added
documentation
Peer Review AssignedHi @accesswatch! Your PR has been automatically paired with @taylorarndt for peer review. For @taylorarndt:This is a great opportunity to practice code review skills! Here's what to look for: Content Quality:
Accessibility:
Documentation:
Review Guidelines:
Resources: Pairing by Learning Room Grouping Engine |
Progress UpdateGreat work, @accesswatch! Current Level: Explorer Available Challenges:
Keep going! |
There was a problem hiding this comment.
Pull request overview
This PR adds troubleshooting guidance explaining why Commit & Push can appear disabled in github.dev after Learning Room maintenance updates, and provides recovery steps across the learner-facing docs and templates. It also includes regenerated html/ artifacts so the published site reflects the new guidance.
Changes:
- Add a new “Common Issues” entry to Appendix J explaining stale
github.devworkspaces and recovery steps. - Add matching troubleshooting guidance to Challenge 5’s “If you get stuck” tables (work.md and the issue template).
- Regenerate
html/outputs (including search index) to reflect the doc updates.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| work.md | Adds a new troubleshooting row for disabled commit/push behavior in github.dev. |
| learning-room/.github/ISSUE_TEMPLATE/challenge-05-make-your-mark.yml | Mirrors the same troubleshooting guidance in the Challenge 5 issue template. |
| docs/appendix-j-cloud-editors.md | Adds a new “Common Issues” subsection documenting the root cause and recovery steps. |
| html/work.html | Regenerated HTML reflecting the updated Challenge 5 troubleshooting table. |
| html/docs/appendix-j-cloud-editors.html | Regenerated HTML reflecting the new Appendix J troubleshooting subsection and on-page link. |
| html/search-index.json | Regenerated search index reflecting updated/added HTML content. |
| |---|---| | ||
| | I am editing on main instead of my branch | Switch to your branch first using the branch dropdown, then edit the file. | | ||
| | I cannot find the edit button | Look for a pencil icon near the top-right of the file view. Screen reader users: the button is labeled "Edit this file". | | ||
| | I am using github.dev and Commit and Push is disabled, or Ctrl+Enter does nothing | You still have write access - the editor's copy of the repository is out of date (your Learning Room receives workshop updates from time to time). Reload the browser tab, or press the period key on the repository page to reopen github.dev. Your unsaved edits are kept in browser storage and come back after the reload. Then check the Accounts button confirms you are signed in, and commit again. If it stays disabled, use the "Edit this file" pencil editor on GitHub.com instead - it always works. | |
| |---|---| | ||
| | I am editing on main instead of my branch | Switch to your branch first using the branch dropdown, then edit the file. | | ||
| | I cannot find the edit button | Look for a pencil icon near the top-right of the file view. Screen reader users: the button is labeled "Edit this file". | | ||
| | I am using github.dev and Commit and Push is disabled, or Ctrl+Enter does nothing | You still have write access - the editor's copy of the repository is out of date (your Learning Room receives workshop updates from time to time). Reload the browser tab, or press the period key on the repository page to reopen github.dev. Your unsaved edits are kept in browser storage and come back after the reload. Then check the Accounts button confirms you are signed in, and commit again. If it stays disabled, use the "Edit this file" pencil editor on GitHub.com instead - it always works. | |
Resolves the root cause behind Community-Access/support#59.
DebeeArmstrong had confirmed write access to her Learning Room (her web commit d261fdd landed on main at 18:56Z), but github.dev showed Commit & Push as disabled. Maintenance sync commits were pushed to every room at 17:04-17:34Z the same day, so any github.dev workspace opened before that went stale; github.dev keeps uncommitted edits in browser storage and disables commit when its base is outdated. Copilot then misreported the situation as missing write access.
Changes:
Checks run: npm run build:html, npm run validate:authoritative-sources (all pass).
The updated Challenge 5 template will be synced to learning-room-template and the eight self-paced-2026 rooms.
🤖 Generated with Claude Code