Bump version 25.08.04 -> 26.03.10

[jacr1]

No description provided.

[github-actions]

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines	Covered	Coverage	Threshold	Status
253	244	96%	0%	🟢

New Files

No new covered files...

Modified Files

File	Coverage	Status
git_hooks/commit_msg.py	94%	🟢
TOTAL	94%	🟢

updated for commit: 0724ced by action🐍

[gemini-code-assist]

Summary of Changes

Hello, 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 performs a routine version update for the git-hooks project. The primary goal is to ensure that all internal references and external documentation examples point to the latest released version of the hooks. This change ensures consistency and directs users to the most current and stable release, improving maintainability and user experience.

Highlights

• Version Bump: The project version has been updated from 25.08.04 to 26.03.10 across relevant configuration files.
• Documentation Updates: Examples and references in the README.md and git_hooks/commit_msg.py have been updated to reflect the new version.
• Configuration Alignment: The pyproject.toml file now correctly specifies the new project version and the bumpver tool's current version.

Changelog

• README.md
  • Updated rev from 25.08.04 to 26.03.10 in the linear-ref pre-commit hook example.
  • Updated rev from 25.08.04 to 26.03.10 in the commit-type-with-linear-ref pre-commit hook example (HTTPS).
  • Updated rev from 25.08.04 to 26.03.10 in the commit-type-with-linear-ref pre-commit hook example (SSH).
• git_hooks/commit_msg.py
  • Updated the version number in the github.com/two-inc/git-hooks README reference URL from 25.08.04 to 26.03.10.
• pyproject.toml
  • Updated the project.version from 25.08.04 to 26.03.10.
  • Updated the tool.bumpver.current_version from 25.08.04 to 26.03.10.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

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 successfully updates the project version from 25.08.04 to 26.03.10. The version string has been consistently updated across README.md, git_hooks/commit_msg.py, and pyproject.toml. All changes are in line with the stated purpose of the pull request, and no functional issues or regressions were introduced.