Don't show commit message body icon for git trailers (only)

[maliayas]

Showing this icon if the commit doesn't have a message body but only a git trailer, creates noise in the commit list:

The icon is useful to signal to the user that "there is more to read" about that particular commit. But in the era of AI, commit messages usually have such trailers:

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Assisted-By: OpenCode:claude-opus-4-6

Then all the commit messages end up with the icon, which render them useless. So it would be nice if Fork could ignore those trailers when deciding to show the icon.

[maliayas]

FWIW: Other issues related to trailers:

• Support for Co-Authored-By #890
• "Wrap Paragraph at Ruler" should respect trailers #2567

[DanPristupov]

Setting aside the rationality of this change (for instance, neither Claude nor Codex add trailers like that for me), to be honest, this change is unlikely to happen because I don't want to parse every single commit message. I don't want to waste CPU cycles, and there will definitely be people who find this behavior confusing. Right now it's straightforward: if there's an icon, there's a description; no icon, no description. But with this, if there's no icon, there might be a description, or there might not.

[maliayas]

Yeah, Claude/Codex doesn't add by default. People is configuring skills for that, e.g. when I commit via running /commit command in my Claude Code session, it writes the commit message together with attribution as git trailers. This is not only me, it's becoming a norm. For example Linux developers published this for contributors:

When AI tools contribute to kernel development, proper attribution helps track the evolving role of AI in the development process. Contributions should include an Assisted-by tag in the following format:

Assisted-by: AGENT_NAME:MODEL_VERSION [TOOL1] [TOOL2]

Where:

• AGENT_NAME is the name of the AI tool or framework
• MODEL_VERSION is the specific model version used
• [TOOL1] [TOOL2] are optional specialized analysis tools used (e.g., coccinelle, sparse, smatch, clang-tidy)

Example:

Assisted-by: Claude:claude-3-opus coccinelle sparse

Also besides AI, there is the very popular "Signed-off-by" lines. GitHub is full of those. Let me share some "random" commits from some random repos:

• rustdesk/rustdesk@9ded8d6
• cjpais/Handy@cfab1dd
• excalidraw/excalidraw@51ca8ab
• anthropics/claude-plugins-official@b01a789
• mozilla/readability@81fac1a
• pydantic/pydantic@dadc815

You can search on your github feed to verify the pattern. Commits are full of signatures.

I don't want to waste CPU cycles

Agreed, but this is easily cacheable, no? Let's say 8 bytes for commit hash and 1 bit for has_actual_commit_message_body; for a project of 1000 commits that makes some dozen KBs. That wouldn't break our hearts I believe 😊

there will definitely be people who find this behavior confusing

A config like "Ignore signatures in commit messages when placing commit message icons" would fix it fine?

[maliayas]

Besides that, I think -as a future vision- Fork should support managing such trailers in the commit window. Because I believe commits can be done more professional on a GUI tool even though commit message may come from AI. So managing/switching authors, signature trailers, AI attribution trailers etc in a simplistic way can be a nice future vision here.