Community Access Support Hub

Open support hub for GIT Going with GitHub learners and alumni.

This repository also serves as a shared support intake for Community Access apps and services that route feedback here automatically.

Start Here

Choose the support path that fits your need:

• Need help solving a blocker: open an issue using one of the support forms.
• Want advice or discussion: use Discussions for Q&A and community collaboration.
• Want to celebrate progress: post wins in Discussions so others can learn from your path.

Purpose

Use this repository for:

• Post-workshop questions
• Setup and troubleshooting help
• Accessibility workflow questions
• Sharing wins and progress updates
• Product feedback and bug reports routed from Community Access apps such as GLOW and Quill

This repository does not host workshop curriculum source files.

Where To Go For Content Changes

• Workshop curriculum and platform changes: https://github.com/Community-Access/git-going-with-github
• Learning Room template changes: https://github.com/Community-Access/learning-room-template
• Security reports: https://github.com/Community-Access/git-going-with-github/security/policy

How To Get Help

1. Open Issues for trackable support requests.
2. Use Discussions for Q&A and community conversation.
3. Include clear reproduction steps and expected behavior.

Support Channels

• Issues: https://github.com/Community-Access/support/issues
• Discussions: https://github.com/Community-Access/support/discussions

Connected App Intake

Some Community Access apps can create issues here automatically through a server-side support-hub connector. Those issues should be treated like any other support request, with the source app, version, and workflow context included in the issue body.

Support Labels

• needs-triage: New issue awaiting first maintainer response
• setup: Installation and environment setup issues
• classroom: GitHub Classroom or assignment flow issues
• accessibility: Screen reader or keyboard accessibility support
• copilot: Copilot or AI-assist questions
• good-first-answer: Great entry issue for community responders
• office-hours: Candidate topics for live office hours
• resolved: Confirmed solved
• escalated: Needs maintainer escalation

Response Targets

• First response: 24 to 48 hours
• Active-cohort triage: daily
• Off-cycle triage: three times per week

Automation

This repository includes support automation:

• First-response assistant on new issues
• Stale queue management
• Weekly support digest every Monday (discussion post with issue fallback)

Community Rules

• Be respectful and constructive.
• Do not post personal data, private links, or secrets.
• If a question involves private student information, ask maintainers for private follow-up.

Maintainer Operations

Maintainers should follow the triage process documented in SUPPORT_PLAYBOOK.md.