TheArchive/tailscale
1
0
Fork 0
mirror of https://github.com/tailscale/tailscale.git synced 2025-05-07 08:07:16 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs/commit-messages.md: merge two 'commit messages' sections (#15668)

Browse Source 
Updates#cleanup

Signed-off-by: Irbe Krumina <irbe@tailscale.com>
This commit is contained in:
Irbe Krumina 2025-04-14 15:20:50 +01:00 committed by GitHub
parent e84522e3e3
commit 624c25bd49
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/commit-messages.md
View File

@ -1,16 +1,12 @@
# Commit messages # Commit messages
There are different styles of commit messages followed by different projects.
This is Tailscale's style guide for writing git commit messages. 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 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 codify existing conventions and promote uniformity and thus ease of reading by
others. Others have stronger reasons, such as interop with tooling or making others. Others have stronger reasons, such as interop with tooling or making
future git archaeology easier. 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 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 shares much in common with the Linux kernel's git commit message style (for
which git was invented): which git was invented):