chore: Optimize CI workflow and prepare for 1.7.0-M2 milestone

[jadamcrain]

Summary

• Eliminate redundant CI runs by removing main branch from push triggers
• Update changelog for upcoming 1.7.0-M2 milestone release
• Add commit message guidelines to CLAUDE.md

Details

With branch protection now enabled on main, all changes must go through PRs. This allows us to remove the main branch from CI push triggers, eliminating duplicate CI runs that occur when PRs are merged.

CI will now run only on:

• Pull requests (validates changes before merge)
• Tags (triggers release workflow)

[gemini-code-assist]

Summary of Changes

Hello @jadamcrain, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on optimizing our continuous integration (CI) workflow and preparing for the upcoming 1.7.0-M2 milestone. I've streamlined the CI process by removing redundant runs on the main branch, leveraging existing branch protection to ensure efficiency. Additionally, I've updated the project's changelog to reflect recent advancements and added new guidelines for Git commit messages to maintain consistency and professionalism.

Highlights

• CI Workflow Optimization: I've updated the CI configuration to prevent duplicate runs on the main branch, ensuring CI only triggers on pull requests and tags. This eliminates redundant CI executions now that branch protection is enabled.
• Changelog Update: I've added new entries to the CHANGELOG.md for the 1.7.0-M2 milestone, detailing recent improvements related to security, quality gates, Maven Central deployment, and release workflow reliability.
• Commit Message Guidelines: I've introduced a new section in CLAUDE.md outlining guidelines for Git commit messages, specifically advising against AI attribution in messages and promoting professional, focused content.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments or fill out our survey to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request prepares for the 1.7.0-M2 milestone by updating the changelog and adding Git commit guidelines. The changes are straightforward documentation updates. I've added one suggestion to CHANGELOG.md to consider adding pull request links for a few items for consistency. The pull request description also mentions optimizing the CI workflow by removing the main branch from push triggers. However, I don't see any changes to workflow files in this pull request. Could you please clarify if those changes are part of this PR or a separate one?

[gemini-code-assist]

For consistency with other entries in the changelog, consider adding links to the corresponding pull requests for these changes if they exist. This helps users and contributors easily track the context and discussion behind each change.

[jadamcrain]

Code Review

This pull request prepares for the 1.7.0-M2 milestone by updating the changelog and adding Git commit guidelines. The changes are straightforward documentation updates. I've added one suggestion to CHANGELOG.md to consider adding pull request links for a few items for consistency. The pull request description also mentions optimizing the CI workflow by removing the main branch from push triggers. However, I don't see any changes to workflow files in this pull request. Could you please clarify if those changes are part of this PR or a separate one?

You're blind. ci.yml was changed.