AI Generated Commit Messages Are Too "Fluffy"

[daryllabar]

Select Topic Area

Product Feedback

Body

The only change in my git commit was renaming a file. Something like, "File was renamed" would seem an appropriate comment, but instead, this is what the AI generated:

The primary change involves the reorganization of the project structure, specifically moving the `Acme_OmApprCostarNa` enum definition from one file to another. This change suggests an effort to improve code organization or to adhere to project naming conventions or architectural guidelines.

### Summary of Changes:
- The `Acme_OmApprCostarNa` enum, initially located in the file `Acme_OmApprCostarNa2.cs`, has been moved to a new file named `Acme_OmApprCostarNa.cs`. This move includes the entire enum definition along with its namespace `Acme.Dataverse.Tables`, all associated attributes, and members. This action indicates a file rename or a structural reorganization within the project, aiming to enhance code maintainability or clarity without modifying the enum's functionality or attributes.

### Detailed Change:
- **File Reorganization**: The `Acme_OmApprCostarNa` enum was transferred from `Acme_OmApprCostarNa2.cs` to a newly created file `Acme_OmApprCostarNa.cs`. This change likely aims to align the file name with the enum name for better readability and consistency within the project's codebase.

This is a simple example, but I have found that in general, there is way too much "fluff" associated with the "Add AI generated commit messages" feature in Visual Studio. Basically every message it generates says that the commit will "enhance code maintainability" or "improve code organization". It needs to be more concise, and too the point.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[daryllabar]

Here is another example (Which is actually wrong, not just full of "fluff") where I just removed an empty line:

The primary change involves the removal of a property from a class within a specific file:

- The nullable boolean property `Hoa` was removed from the class `Acme.Dataverse.Plugin.Poco.SpecForm` located in the `SpecForm.cs` file. This modification could impact how instances of `SpecForm` handle the `Hoa` property, potentially affecting any logic or functionality that relied on this property.

Reference to the code change:
- Removal of `Hoa` property from `Acme.Dataverse.Plugin.Poco.SpecForm` in `SpecForm.cs`.

If I had indeed actually removed a property, then something like the last line should have been all that was in the commit,

- Removal of `Hoa` property from `Acme.Dataverse.Plugin.Poco.SpecForm` in `SpecForm.cs`.

because of course, removing an property "could impact how instances of SpecForm handle the Hoa property, potentially affecting any logic or functionality that relied on this property."