Tag
7 articles tagged #Git.
P.01Trunk-based development wins on speed and CI/CD fit for most teams. Git Flow still earns its keep for versioned software. The verdict, by criterion.
P.02Bruno stores API collections as plain .bru text files in your git repo, no account or cloud sync needed. Here's how it compares to Postman and why teams switch.
P.03Git worktrees give you multiple branches checked out in separate directories at once. No stashing, no context switching, no losing your place.
P.04Structured commit messages unlock automatic changelogs, version bumps, and release notes. The full setup, from commitlint hooks to shipping in CI.
P.05How we built a Git-to-Supabase content pipeline with SHA-256 delta sync, Edge Functions, and GitHub Actions. Full architecture and code walkthrough.
P.06Trunk-based, Git Flow, GitHub Flow: here is the simple Git workflow that works for teams under 10, why Git Flow struggles at that size, and the mistakes to avoid.
P.07Splitting a growing blog into its own repo, linked by a Git submodule, fixes merge conflicts and CI noise. Here is our exact setup for 130+ posts.