From 624c25bd4936f5388393487065d427d73169904e Mon Sep 17 00:00:00 2001 From: Irbe Krumina Date: Mon, 14 Apr 2025 15:20:50 +0100 Subject: [PATCH] docs/commit-messages.md: merge two 'commit messages' sections (#15668) Updates#cleanup Signed-off-by: Irbe Krumina --- docs/commit-messages.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/docs/commit-messages.md b/docs/commit-messages.md index 36b539689..22a6e67ce 100644 --- a/docs/commit-messages.md +++ b/docs/commit-messages.md @@ -1,16 +1,12 @@ # Commit messages +There are different styles of commit messages followed by different projects. This is Tailscale's style guide for writing git commit messages. - As with all style guides, many things here are subjective and exist primarily to codify existing conventions and promote uniformity and thus ease of reading by others. Others have stronger reasons, such as interop with tooling or making future git archaeology easier. -# Commit Messages - -There are different styles of commit messages followed by different projects. - Our commit message style is largely based on the Go language's style, which shares much in common with the Linux kernel's git commit message style (for which git was invented):