Forumics logo Forumics
Issue 01

Back to issue

All Zed known issues

CLAIM C169 Supported 2026-11-20

GitHub issue #26643 in zed-industries/zed, opened 2025-03-13 by ronnelreposo, records a report that when committing changes, lines in the commit message that start with # are omitted, and if the message consists of only one line starting with #, an error occurs stating Aborting commit due to empty commit message; the report was filed against Zed v0.177.7 on macOS 15.3.1, with an expected behavior that hash-starting lines be retained and a single hash-starting line not cause an error.

Verbatim Excerpts from Cited Records
“When committing changes, lines in the commit message that start with # are omitted. If the commit message consists of only one line that starts with #, an error occurs stating “Aborting commit due to empty commit message”.”
— ronnelreposo · zed-industries/zed (issue 26643 opening body, Summary section) · 2025-03-13T05:22:19Z ·GitHub Issue ↗
“# A header commit message - commit detail a - commit detail b”
— ronnelreposo · zed-industries/zed (issue 26643 opening body, Summary section, reproduction steps) · 2025-03-13T05:22:19Z ·GitHub Issue ↗
“Failed to commit: Aborting commit due to empty commit message.”
— ronnelreposo · zed-industries/zed (issue 26643 opening body, Summary section, Actual Behavior) · 2025-03-13T05:22:19Z ·GitHub Issue ↗
“- Lines starting with # should be retained in the commit message. - A commit message with a single line starting with # should not cause an error.”
— ronnelreposo · zed-industries/zed (issue 26643 opening body, Expected Behavior section) · 2025-03-13T05:22:19Z ·GitHub Issue ↗
Counter-record: Issue open as of the fetch; 16 comments were read. The author noted escaping the hash with a backslash as a workaround. Bjorn-Eric-Abr replied that hash lines are comments in a commit message; the author tried commit.cleanup verbatim and whitespace, and reported CLI and VSCode respect the setting while Zed continues to strip hash lines. Maintainer cole-miller replied on 2025-03-13 that Zed passes cleanup strip unconditionally and that it might be good to remove it so the setting is respected. Users reproduced the behavior on Zed Nightly v0.223.0 in 2026-02-04, Zed 0.221.5, Zed v0.223.3 stable and Zed 1.15.0 on 2026-08-18. The author on 2026-05-08 framed the stripping as data loss when ticket references such as hash 9175 are removed from the header. mchisolm0 on 2026-05-14 reported the backslash workaround no longer works on Zed v1.3.0 nightly, and J-Klinke on 2026-11-19 offered to fix it, proposing a git.commit_message_cleanup setting. No fix merged appears in the surveyed thread. The claim documents only the original report, not a verified current state. Falsification probe: If GitHub issue #26643 is deleted without archive, if the author edits the opening body so the quoted sentences no longer match verbatim, or if the author posts a retraction of the report, this claim drops to Withdrawn. Audit verification: Verified 100% continuous verbatim substring against official GitHub REST API by scripts/verify_claim_verbatim.py.