summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBen Sima <ben@bensima.com>2025-12-01 13:25:25 -0500
committerBen Sima <ben@bensima.com>2025-12-01 13:25:25 -0500
commit1045882e399309067c77d528dcc4d7cef3e4052c (patch)
treea0e31b7bbbd19c8c9efcf8bc4f1de4ab10b781f3
parent6936309247e76c7e0e36c67b77eeea8df388d050 (diff)
Remove .gitmessage
The intention was for this to be instructions for the coding agents to create commit messages, but they never read this file, so just delete it.
-rw-r--r--.gitmessage26
1 files changed, 0 insertions, 26 deletions
diff --git a/.gitmessage b/.gitmessage
deleted file mode 100644
index 1eb44e6..0000000
--- a/.gitmessage
+++ /dev/null
@@ -1,26 +0,0 @@
-
-# Summarize change in 50 characters or less
-#
-# More detailed explanatory text, if necessary. Wrap it to about 72
-# characters or so. In some contexts, the first line is treated as the
-# subject of the email and the rest of the text as the body. The
-# blank line separating the summary from the body is critical (unless
-# you omit the body entirely); various tools like `log`, `shortlog`
-# and `rebase` can get confused if you run the two together.
-#
-# Explain the problem that this commit solves. Focus on why you are
-# making this change as opposed to how (the code explains that).
-# Are there side effects or other unintuitive consequences of this
-# change? Here's the place to explain them.
-#
-# Further paragraphs come after blank lines.
-#
-# - Bullet points are okay, too
-#
-# - Typically a hyphen or asterisk is used for the bullet, preceded
-# by a single space, with blank lines in between, but conventions
-# vary here
-#
-# If applied, this commit will...
-# Why was this change made?
-# Any references to tickets, articles, etc?