0 views collected around this technical thread.
This article explains the widely used Git commit message convention, detailing the subject prefixes such as feat, fix, docs, and others, their meanings, example usages, and the benefits of adopting a standardized format for clearer project history and automation.
This guide explains Git branch naming conventions, maps branches to development environments, outlines a standard merge workflow, details commit message standards—including Angular guidelines and a simplified format—and provides a sample .gitignore, offering practical tips for clean, maintainable code management.
The author recounts submitting a Go PR to fix a benchmark timeout overflow bug, detailing the code review feedback, overflow detection issues, testing strategies, and proper commit‑message conventions, ultimately sharing insights from a largely unsuccessful contribution attempt.
This guide explains how to create repository‑specific and global GitLab server hooks that validate commit messages against a custom pattern, showing step‑by‑step configuration, a Go pre‑receive script, and verification commands to ensure only properly formatted commits are accepted.
This article explains why high‑quality code review is vital for software teams, outlines the responsibilities of submitters and reviewers, emphasizes clear commit messages and test plans, and offers practical guidance for giving constructive and appreciative feedback to improve code quality and team collaboration.
This article explains why code review is vital for software teams, outlines the responsibilities of submitters and reviewers, emphasizes clear commit messages and test plans, and offers guidance on giving constructive and positive feedback to foster a healthy feedback culture.
The article explains the importance of establishing Git commit message and branch naming standards, demonstrates the benefits of structured conventions, provides concrete examples and regex patterns, and shows how to enforce them with Git hooks such as Bitbucket's Yet Another Commit Checker.
The team introduced an Angular‑style Git commit‑message standard—type(scope): subject in Chinese—and built a webhook‑based monitoring service that validates pushes, alerts violations, tracks diff size and deletions, stores metrics, and visualizes compliance, improving traceability, readability, and automated changelog generation.
This article explains the conventional Git commit message format, its components and benefits, and demonstrates how to enforce the standard using tools such as Commitizen, commitlint, husky, and standard-version, providing practical examples and configuration snippets for developers.
The article describes a low‑cost solution that uses Git hooks and a custom CLI tool to automatically embed work‑item IDs from branch names or interactive selection into commit messages, enabling seamless traceability between code commits and requirements or defects and simplifying automated testing and team collaboration.