Please use verbose commit descriptions

[dtor]

Hi,

I just started looking at avante code but I noticed that majority of CL descriptions are essentially one-liners that do not explain neither the purpose of a change nor provide reasons why the change is done in a certain way. This makes it hard for external contributors to work with the code base, since good commit descriptions is the only way to communicate design decisions that does not require searching through github interface on the off chance there is an issue attached to the pull request that maybe has a decent explanation of what the change intended to achieve.

Thanks!

[dtor]

I guess this is idiotic github behavior wrecking repository history so the resulting repository is only useful with github web interface. It reduces commits like:

commit 6628f4c07dfa73ae1d2cadca8b1855a039a5513f (github/delete-dead-code)
Author: Dmitry Torokhov <[email protected]>
Date:   Fri Jul 11 22:44:28 2025 -0700

    refactor(llm): remove dead code summarizing threads and generating todos

    The last user of Llm.summarize_chat_thread_title() was commented out in
    bc403dd ("feat: ReAct tool calling (#2104)") and the comment itself was
    removed in 801adc4 ("feat: delete tool use messages tool (#2158)")

    Remove the dead code.

to completely useless

commit 0c6a8f5688cefb37259d3404f0403075e033a182 (origin/main, origin/HEAD, main)
Author: Dmitry Torokhov <[email protected]>
Date:   Sun Jul 13 19:14:40 2025 -0700

    refactor(llm): remove dead code summarizing threads and generating todos (#2439)

It is even worse when originally there was a commit chain splitting large change into a series of logically separate steps. Can it be taught to preserve CL history properly? Is this the result of "squash merging"?