Get to Know GitHub 8: Wrap-up

Slides 16 and 17 (before you go, questions). 0:50 to 0:54 for the wrap-up, then Q&A from 0:54 to 1:00, plus what happens after.

What this section has to do

Land the rule one more time, give people a clear homework with a date, tell them where to get help, and point at what else exists without teaching it.

Talk track

The rule. If you've built it and you might use it again, it goes in AIMCLEAR's GitHub.

Homework. Go to github.com/aimclear/employee-repo-template and hit Use this template > Create a new repository. Set Owner to AIMCLEAR and pick Private. Then move everything you've built that you still use into it by [date].

Stuck? Email me at timothy@aimclear.com, or grab anyone on the dev team. I'm happy to field them, and no question is too basic.

What else exists (from the March design doc). Two things you already saw today have names, if you want to look them up later. Actions are automatic checks, like Gitleaks checking every push, browser uploads included. Branch protection is why main wouldn't take a direct edit in the demo. The template brings the Gitleaks check, and an org rule protects main.

Want more? Anyone who wants the command line, more on Actions, or help getting Claude Code working with GitHub, grab time with me.

Then open floor.

Open items before Thursday

• The homework [date] waits on the SysAdmin's answer. If there's no answer by Wednesday, pick one and say it's set with her.

Follow-up email draft

To send after the session, to the same list as the invite.

Subject: Get to Know GitHub follow-up: recording, homework and help

Hi all,

Thanks for joining today's Get to Know GitHub session. Here's the recording for anyone who missed it or wants to rewatch: [recording link].

The rule: if you've built it and you might use it again, it goes in AIMCLEAR's GitHub.

Your homework, by [date]: go to github.com/aimclear/employee-repo-template, hit Use this template > Create a new repository, set Owner to AIMCLEAR and visibility to Private, and move in everything you've built that you still use.

Never commit passwords, API keys, client data or personal details. If something slips in, tell the dev team right away. Nobody's going to be mad, we just need to move fast.

If you use Claude, you can have it do the clicking. Try: "Save this script to my repo on a new branch and open a PR for review." Claude opens the pull request. Add a note on what the script is for, and someone on the dev team will review it.

Questions go to me at timothy@aimclear.com or anyone on the dev team. No question is too basic.

-- Timothy

FAQ (for the email or a pinned doc)

• Do I need to know the command line? No. The browser does everything you need.
• What counts as "built it"? Scripts, Apps Script, little HTML tools, prompt files and Claude project instructions you reuse. If you might use it again, it counts.
• Can I keep it in Drive too? Sure, but GitHub is the copy that counts.
• Who reviews my PRs? Someone on the dev team. Add a note on what the script is for and request a dev team reviewer. You don't need to judge the code yourself.
• I committed a key. Now what? Tell the dev team right away. Deleting the file doesn't fix it, because the key has already left your laptop. It has to be rotated, which means the old key gets turned off and a new one is made.
• Can I make a repo public? Not without asking first.
• Can Claude do this for me? Yes. Claude opens the pull request. Add a note on what the script is for, and someone on the dev team will review it.

Cheat sheet (handout)

• Repo: the project, with every version
• Branch: your workspace
• Commit: a saved version with a note
• Pull request: ask for review before it goes live
• Main: what's live
• Never commit: keys and passwords, client data, personal stuff
• Committed a secret? Tell the dev team right away
• Always: AIMCLEAR org, private, a README on every script
• Or just tell Claude what you're trying to do

After the session

• Post the recording link with the follow-up email.
• Clean up the practice repo: merge or close every open training PR and delete the add-firstname-lastinitial branches.
• Keep the people/ files if you want a roster of who's been through it, or clear them (keep the placeholder file) so the practice repo starts clean.
• Check employee-repo-template still has the Gitleaks workflow and Template repository is still on.
• Close the demo PR and delete its branch if it was only for the session.
• A week before the deadline, check which people have a repo in the org and nudge the rest.

Done when

Everyone leaves knowing the rule, the homework and the date, and who to ask.