Avoid ai_tools Spam in Commits

Keep it Simple

When you're working on a project, your commit history should tell a story. But, if your commits are filled with ads for new ai_tools, it's just noise. You're annoying your teammates and making it harder to see what's actually changing.

So, what should you do instead? Focus on writing clear, concise commit messages that describe the changes you're making. This makes it easier for everyone to understand the codebase.

Best Practices

• Write commit messages in the imperative mood (e.g. 'Fix bug' instead of 'Fixed bug')
• Keep your commit messages short and to the point
• Avoid using commit messages as a way to advertise new tools or technologies

For example, instead of 'Added new ai_tool to project, it's really cool!', say 'Updated dependency to fix compatibility issue'. This way, you're providing useful information without cluttering the commit history.

And, if you're using a new ai_tool that you think is really useful, consider writing a blog post or creating a tutorial to share your knowledge instead of spamming your teammates with ads in the commit history.

But, some might argue that advertising new ai_tools in commits can help spread knowledge and awareness. While this might be true, it's not the right place to do it. Your commit history should be a record of changes, not a marketing channel.