From 1045882e399309067c77d528dcc4d7cef3e4052c Mon Sep 17 00:00:00 2001 From: Ben Sima Date: Mon, 1 Dec 2025 13:25:25 -0500 Subject: 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. --- .gitmessage | 26 -------------------------- 1 file changed, 26 deletions(-) delete mode 100644 .gitmessage (limited to '.gitmessage') 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? -- cgit v1.2.3