Saidinesh Narisetti·Oct 18Enforcing Commit Message Standards: From Local Git Hooks to GitHub Actions CIMaintaining a uniform Git commit history is vital for traceability across agile teams. When commits follow a structured pattern like…
Dev Talk·Oct 8Git Commit Best Practices: add -p, Messages & .gitignoreMost Git commit best practices come down to one habit: decide what goes into a commit before you type git commit, not after. Part 1…
Irham Dinata·Sep 30How to Add New Changes to an Existing Commit and Rename ItSometimes you have already created a Git commit, but then realize that you still have some changes that should have been included in that…
Irham Dinata·Sep 29How to Clone a Git Repository Without Its Commit HistorySometimes, you want to reuse the latest version of an existing Git repository but do not want to bring its commit history with you.
Cleo Excellen Iskandar·Sep 21Delapan Orang, Satu Repository, Satu Alur KerjaMenulis kode yang benar ternyata hanya separuh dari tantangan dalam membangun sebuah sistem. Tantangan lain yang ternyata perlu dihadapi…
Susii Komalasari·Sep 16Catatan Belajar Git: Dari Local Repository hingga GitHubMemahami workflow sederhana untuk mengelola project, menjalankannya di localhost, mencatat perubahan dengan Git, dan menyinkronkannya ke…
InLevel Up CodingbyAbdullah @writer·Aug 28Rewriting Git History Safely: Amend, Cherry-Pick, Squash, and Merge StrategyMost teams treat Git history as exhaust. Then something breaks in production, someone runs git log on the release branch, and finds forty…
Anil Poudyal·Aug 19Conventional Commits: The Only Cheatsheet You NeedStop writing commits like “fix”, “final fix”, “asdf”, and “please work”. Use this format instead, and your git log actually becomes useful.
TUSHAR KUMAR·Aug 18Git Commit Messages: One Small Thing I Wish I Learned EarlierLearn this if you want to write better commit messages.
