Developer onboarding: workflow setup

[kjkaustin]

Checklist for getting a new developer fully set up and into the dev workflow.

Access

• Accept GitHub org invite
• Enable 2FA on GitHub account
• Added to developers team
• Confirm access to relevant repos

Local Setup

• Clone assigned repos
• Copy .env.example → .env, fill in values (get secrets from Kevin)
• Read CLAUDE.md in each repo before touching code

Tools

• Install gh CLI and authenticate (gh auth login)
• n8n access: https://n8n.mightyandtrue.com (get credentials from Kevin)
• Supabase access: shared instance (get credentials from Kevin)

Git Workflow

• Understand branch naming convention: your-name/short-description
• Never push directly to main — branch protection is enforced
• Open a PR, reference the related issue with Closes #N
• 1 approval required before merging

Project Board

• Review the Engineering project board: https://github.com/orgs/mightyandtrue/projects/2
• Understand Planning vs Backlog vs This Week columns
• Pick up first issue and move it to This Week

[kjkaustin]

Pre-call setup for new developer

Hey — before our call, a couple of quick things to set up on your end.

1. Check if you have an SSH key

Open Terminal and run:

cat ~/.ssh/id_ed25519.pub

If you see a long string starting with ssh-ed25519, copy the whole thing and send it to me.

If you get "No such file or directory", run this first to generate one:

ssh-keygen -t ed25519 -C "yourname@mightyandtrue.com"

Just hit Enter through all the prompts to accept defaults. Then run the cat command above and send me the output.

2. Install the GitHub CLI

brew install gh

Then authenticate:

gh auth login

Follow the prompts — choose GitHub.com, HTTPS, and log in via browser.

3. That's it for now

Once I have your public key I'll get your server access set up before our call. We'll walk through the rest together.