Post-Workshop Teardown Checklist

Use this checklist after each workshop cohort completes the course.

Within 24 hours of Day 2

• Export grades from GitHub Classroom (Classroom Settings, Download Grades)
• Verify all students have at least one merged PR
• Note any students who need follow-up (incomplete capstone, missing challenges)
• Send post-workshop survey link (see ANNOUNCEMENT.md for template)

Within one week

• Review student feedback from surveys
• Move any private registration exports, accommodation notes, grade exports, or follow-up notes to Community-Access/git-going-student-success
• Archive the classroom (Classroom Settings, Archive)
• Close any remaining open issues across student Learning Room repositories (or leave them open if students want to continue practicing post-workshop)
• Merge or close any abandoned student PRs with a kind comment
• Update the student roster in the main repo if students should retain access for ongoing contribution

Clean up student repositories

GitHub Classroom creates one repository per student per assignment. After the course:

1. Download any student work that should be preserved
2. In Classroom settings, click "Delete all student repositories" (this is irreversible)
3. Alternatively, keep the repositories for students who want to continue contributing

Update facilitator notes

• Document any chapter sections that confused multiple students
• Note any technical issues encountered (e.g., Copilot activation problems, clone failures)
• File issues in the git-going-with-github repo for curriculum improvements
• Update the FACILITATOR.md with any new troubleshooting tips

Prepare for next cohort

• Review and incorporate feedback from this cohort
• Update roster-template.csv with new student list
• Create a fresh classroom following README.md
• Test all invite links with a test account

Authoritative Sources

Use these official references when you need the current source of truth for facts in this chapter.

• GitHub Docs, home
• GitHub Changelog
• About Git
• GitHub flow
• About pull requests
• About issues
• Contributing to a project

Section-Level Source Map

Use this map to verify facts for each major section in this file.

• Within 24 hours of Day 2: GitHub Docs, home, GitHub Changelog, About Git, GitHub flow, About pull requests
• Within one week: GitHub Docs, home, GitHub Changelog, About Git, GitHub flow, About pull requests
• Clean up student repositories: GitHub Docs, home, GitHub Changelog, About Git, GitHub flow, About pull requests
• Update facilitator notes: GitHub Docs, home, GitHub Changelog, About Git, GitHub flow, About pull requests
• Prepare for next cohort: GitHub Docs, home, GitHub Changelog, About Git, GitHub flow, About pull requests