Updated copyright period to be inclusive of 2025

[tclose]

Updates the copyright period to 2017-2025 (mainly just an excuse to trigger a release)

[gemini-code-assist]

Summary of Changes

Hello @tclose, 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 primarily updates the copyright year within the project's documentation configuration. This seemingly minor change also serves the strategic purpose of initiating a new software release.

Highlights

• Copyright Update: The copyright period in the project's documentation configuration has been updated to reflect the year 2025, extending the previous period.
• Release Trigger: This change is intentionally made to serve as a trigger for a new release of the project.

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 updates the hardcoded copyright year in the Sphinx documentation configuration. My review provides a suggestion to improve the long-term maintainability of this configuration by dynamically generating the current year. This would eliminate the need for manual updates in the future.

[gemini-code-assist]

While this change works, hardcoding the end year for the copyright notice creates a maintenance task for the future. To make this more maintainable and avoid needing to update it again, you can dynamically set the current year. This will ensure the copyright year is always up-to-date automatically.

Here's how you could implement this, following best practices for code organization¹:

# At the top of docs/conf.py (e.g., line 10) import datetime # ... # In the project information section (line 27) copyright = f"2017-{datetime.date.today().year}, Neurodocker Developers"

This approach improves long-term maintainability by removing the need for manual yearly updates.

Style Guide References

Footnotes

1. PEP 8 advises that imports should usually be on separate lines and placed at the top of the file, just after any module comments and docstrings, and before module globals and constants. ↩

[Remi-Gau]

FYI: the year can be removed alltogether: https://hynek.me/til/copyright-years/