Mention CODING_STANDARDS in CONTRIBUTING

[laserkelvin]

PhysicsNeMo Pull Request

Description

This PR updates the CONTRIBUTING.md with two things:

• Bump the example license header year to match the current codebase (2023 - 2025)
• Guide potential contributors to the CODING_STANDARDS folder to align on coding style

Checklist

• I am familiar with the Contributing Guidelines.
• New or existing tests cover these changes.
• The documentation is up to date with these changes.
• The CHANGELOG.md is up to date with these changes.
• An issue is linked to this pull request.
• If I am implementing a new model or modifying any existing model, I have followed the Models Implementation Coding Standards.

Dependencies

N/A

Review Process

All PRs are reviewed by the PhysicsNeMo team before merging.

Depending on which files are changed, GitHub may automatically assign a maintainer for review.

We are also testing AI-based code review tools (e.g., Greptile), which may add automated comments with a confidence score.
This score reflects the AI’s assessment of merge readiness and is not a qualitative judgment of your work, nor is
it an indication that the PR will be accepted / rejected.

AI-generated feedback should be reviewed critically for usefulness.
You are not required to respond to every AI comment, but they are intended to help both authors and reviewers.
Please react to Greptile comments with 👍 or 👎 to provide feedback on their accuracy.

[greptile-apps]

Greptile Summary

Updates contributor documentation to reflect current year and improve guidance on coding standards.

• Updated license header copyright year from 2023-2024 to 2023-2025
• Added new "Coding Style" section directing contributors to the CODING_STANDARDS directory for detailed guidelines on code organization and model development rules

Important Files Changed

Filename	Overview
CONTRIBUTING.md	Updated license header year to 2025 and added new Coding Style section directing contributors to CODING_STANDARDS directory

[greptile-apps]

Greptile's behavior is changing!

From now on, if a review finishes with no comments, we will not post an additional "statistics" comment to confirm that our review found nothing to comment on. However, you can confirm that we reviewed your changes in the status check section.

_{This feature can be toggled off in your Code Review Settings by deselecting "Create a status check for each PR".}

[coreyjadams]

/blossom-ci