GitHub

Code · Git · CI/CD

The source of truth for code, changes, releases, issues, and deployment triggers.

Why it earns a place

Why I use it

I want every useful project to have a history I can inspect, revert and hand to another person. GitHub also becomes the bridge between local work, Pages CMS, automated checks, and Cloudflare/Vercel deployments.

Use cases

Best for

Keeping public and private repositories versioned
Triggering deployments from a main branch
Publishing small open-source utilities
Tracking issues and release notes without another project manager

Start small

Quick start

01
Create the repository
Start private unless you already know the code should be public. Add a README, license only when appropriate, and a .gitignore before the first push.
02
Push a clean main branch
Commit only files that belong in source control. Never commit .env files, API keys, exports containing private data, or local build artifacts.
03
Connect the host
Authorize Cloudflare Pages or Vercel to read the repository. Treat preview deployments as disposable review environments and main as production.

Repeatable workflows

Things I come back for

Make a tool public

Before flipping visibility, scan the full Git history for secrets, remove proprietary datasets, add setup instructions, and choose an explicit license.

1
Scan the repository and history for secrets or private exports.
2
Add a minimal README with setup, purpose, and known constraints.
3
Choose a license intentionally, then change repository visibility.

GitHub Actions

Use Actions for repeatable checks, scheduled exports, linting, tests or data jobs that should not depend on your laptop being awake.

1
Create one workflow for one repeatable job.
2
Store credentials in repository or environment secrets.
3
Run it manually once, inspect logs, then add triggers or a schedule.

Releases

For desktop tools and extensions, tag meaningful versions and attach packaged artifacts so a repository also documents the product lifecycle.

1
Update the version and release notes.
2
Create and push a matching Git tag.
3
Publish the release with the packaged artifact and a concise changelog.

Reference

Links