New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto generated comments #39754
Auto generated comments #39754
Conversation
@codemakerai-dev Please sign the Contributor License Agreement! Click here to manually synchronize the status of this Pull Request. See the FAQ for frequently asked questions. |
Thanks for the pull-request, but I'm afraid we prefer to keep the codebase manually documented. I think your tool could be very useful for folks that are learning the codebase or need additional help with certain parts, but I'm afraid it adds quite a lot of noise to document every part of the codebase automatically. Thanks again for the offer and good luck with the product. |
I totally get where you're coming from with preferring manual documentation. It's all about finding what works best for the team. Thank you for consideration. |
This comment was marked as abuse.
This comment was marked as abuse.
Sorry to barge in. @codemakerai-dev I would love to know how you did it. Can you point me to your repo? |
It is not free or open source. They literally advertised Codemaker AI, which makes this 10x more funnier. Starts at 7.50 bucks, now learn how to not write comments with a shy amount of fee. |
Let me clarify three things:
|
...wait so comments |
I'm going to lock this one now as Spring Boot's issue tracker isn't really the place to discuss CodeMaker AI's comment generation and business model. Best of luck with the project, @codemakerai-dev. |
Summary
This code change adds comments to the entire Spring Boot code base. The content of this PR has been created entirely using a custom fine-tuned AI model.
We are conducting large-scale experiments of our tool by running it on millions of lines of code to identify any bugs or errors. When run against this code base the tool reached a compilation success rate of 99.9%.
We had a choice to either discard this code or publish it and offer it as a contribution. We chose the latter and decided to open this Pull Request.
At any point, I do not expect the Pull Request will get merged in this shape, even from the perspective that it would be unrealistic to merge it and resolve any potential conflicts. The change also introduces violations of check style, that we would have to automatically solve.
What we did consider though and this is completely open for discussion are the following.
Providing that you would find such contribution beneficial.
We can offer to recreate the code change either partially or fully once we address and re-iterate on the product making it customized to your specific project. We can also re-create this entire step on any other repository.
Split the pull request and re-use the changes that you find useful. We can freely re-do the same operation on any part of the code.
How this change was created?
We executed a task that was completed by our product autonomously, using a custom fine-tuned model. The model that we used is not generally available at this time and is being evaluated.
I am completely open to feedback and discussion, we will use it to re-iterate on our product and improve it.