GitHub Release Guide

How to create a GitHub Release — both via the web UI and via CLI. Prerequisites A GitHub repository Git installed: https://git-scm.com/ For CLI: GitHub CLI (gh): https://cli.github.com/ Login with: gh auth login UI Method (Web) Step 1: Commit and push git add . git commit -m "feat: add new feature" git push origin main Step 2: Create and push a tag git tag v1.2.3 git push origin v1.2.3 Step 3: Create Release on GitHub Go to your repo → find Releases in the sidebar Click Create a new release Fill in Tag version, Release title, Description Click Publish release CLI Method Step 1–2: Same as above (commit, tag, push) Step 3: Create release via CLI gh release create v1.2.3 \ --title "v1.2.3" \ --notes "### Bug Fixes\n- Fix JSON special character handling (#2481)" Or use a Markdown file: ...

2025-07-27 · 1 min · Derek

Git & Jekyll Workflow Notes

Git Workflow Stage all changes at once git add . . means add all modified or new files. Correct commit message format (to avoid commitlint errors) git commit -m "feat: update about page and fix broken icons" Type Purpose feat New feature fix Bug fix docs Documentation changes style Formatting (no logic change) refactor Code refactor (not a bug fix) chore Misc tasks (no functional impact) Commit message must follow the format type: message, otherwise commitlint or husky will block the commit. ...

2025-07-19 · 1 min · Derek