Option to collapse or truncate verbose Git Notes in the Commit View
Automated tools (like git-ai) increasingly use Git Notes to store large, machine-readable data payloads. When mapped to SmartGit's UI via smartgit-notes, these raw notes clutter the Commit Details view, creating massive walls of text that push standard commit information off-screen. See example below (note how the "branches" section has been pushed to the bottom of the text chunk).
Request
Please add a way to manage this UI clutter so users can keep tracking tools enabled without sacrificing readability. Potential solutions:
- Collapsible Notes: Render note text inside an accordion that defaults to "collapsed", showing only the note category or first line.
- Truncation Toggle: A UI preference to only display the first line/paragraph of a note.
- Regex Filtering: Perhaps extend the existing
graphMessageRegexconfiguration to filter or truncate what displays in the Commit Details view, not just the Graph view.
Example of the clutter shown in commit view:
VNA-666: rebundle OpenAPI specs after shared error updates
AI-attribution:
.acme/openapi-reachability-bundled.yaml
s_bbd3531718a57a::t_752916422b0889 237,245,251,256,262,267,273,278,284,289,295,300,319,327,333,338,344
.acme/openapi-sim-swap-bundled.yaml
s_bbd3531718a57a::t_752916422b0889 147-259
.acme/openapi-kyc-match-bundled.yaml
s_bbd3531718a57a::t_752916422b0889 299,307,313,318,324,329,335,340,346,351,357,362,381,389,395
[^many lines like those ^]
---
{
"schema_version": "authorship/3.0.0",
"git_ai_version": "1.4.8",
"base_commit_sha": "cedf23cca61eb8b512c52848675049df93ecd7a6",
"prompts": {},
"sessions": {
"s_bbd3531718a57a": {
"agent_id": {
"tool": "opencode",
"id": "ses_1e9293b65ffeBYXVzwIZ8UJ2Iy",
"model": "gpt-5.3-codex"
},
"human_author": "raton.perez "
}
}
}
branches VNA-666-SAAdv2-openapi-errors, origin/VNA-666-SAAdv2-openapi-errors
Customer support service by UserEcho
A possible quick workaround we could implement for 26.1 is a Low-Level Property that truncates notes at N characters. Would that be acceptable for you?
May be if it's a quick fix so we could see the "AI attribution" string which is the first useful bit of info. The other one is the list of file names attributed to AI (the rest of stuff not so much) but with fixed trucation would be difficult to keep only the filenames, it's a dynamic list and there's a lot of useless numbers there.
Also annoying is that the branches line is for some reason pushed to the bottom.
Right, with fixed truncation, this won't work. Overall, this sounds like a more elaborate and configurable post-processing of Git Notes content to determine what should be displayed.
> Additionally, it's annoying that the branches line is, for some reason, pushed to the bottom.
This depends on how important you consider the Notes information. The notes that SmartGit creates are usually something you trigger manually, and you don't want them buried behind a long list of branch details that are always computed. So it's reasonable to show them before.
These auto-generated Notes that you encounter seem to be less important (even when cleaned) and should be displayed later. So it sounds like another option would be needed.