💬 Discuss and agree about design before contribution
I am part of the Murex organization, we have a bit of time this summer, and we would like to contribute to your project. We want to extend it with the following features:
More possibilities to customize the commit message itself: to include footers, a "Why" body header, and more details in the body We have been thinking of a more advanced template with named sections that could be provided by custom prompts or by command line options.
An option to commit without user validation, using an extra command line option
Support for other LLMs backend, we plan plugin the tool on our own RAG
Support for Perforce because most Murex developers rely on this VCS. Obviously not all git features will be supported. We could create an abstraction for the different VCS and let the tool switch to Perforce with an option, or a configuration. Another way would be to make the tool VCS agnostic, move all git commands out of the tool, and create shell wrappers to give it the diff through stdin, receive the message from stdout, and commit. I'm not sure how this would work with githook though.
To avoid rework, I would like to start a conversation to get your feedback about the proposed features and design before we send pull request.💬 Discuss and agree about design before contribution
Why?
We have 2 main use cases:
Code Katas with TCR: In this workflow, the TCR tool commits very often. That's why we want the possibility to commit without validation. Currently we don't have any meaningful messages for these commits. We want to use AI-generated conventional commits instead. We also want to have the possibility to specify sections of the commit messages template through the command line (footer meta info, whether it's passing or failing...) We would like AI to give us the list of named baby steps that the trainees used in the details of the message body.
Inhouse Murex development: 'easy' conventional commits would increase the quality of the commit log. Murex developers are relying on Perforce VCS, that's why we need a support for perforce. Also, for security reasons, they cannot rely on GPT directly, we need to plug the tool to our on-premise RAG.
Feature request
💬 Discuss and agree about design before contribution
I am part of the Murex organization, we have a bit of time this summer, and we would like to contribute to your project. We want to extend it with the following features:
To avoid rework, I would like to start a conversation to get your feedback about the proposed features and design before we send pull request.💬 Discuss and agree about design before contribution
Why?
We have 2 main use cases:
Alternatives
Additional context
No response