Canary CICD Pipeline

[sr2echa]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @sr2echa, 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 introduces a new pull request template to standardize PR descriptions and makes a minor adjustment to the ruff linter configuration in the backend. While the title suggests a "Canary CICD Pipeline," the current changes primarily focus on documentation and tooling setup rather than direct pipeline implementation.

Highlights

• New Pull Request Template: A standardized template (.github/PULL_REQUEST_TEMPLATE.md) has been added to guide authors in providing comprehensive information for pull requests, including sections for summary, changes, testing, and deployment notes.
• Ruff Configuration Refactor: The ruff linter configuration in backend/pyproject.toml has been updated to move the select and ignore rules under a new [tool.ruff.lint] subsection, aligning with ruff's updated configuration structure.

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. 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 introduces a pull request template and updates the Ruff linter configuration. The new PR template is a great addition for standardizing contributions, and I've suggested adding a checklist to further improve the process. The update to pyproject.toml correctly moves Ruff's linting configuration to the [tool.ruff.lint] section, which aligns with recent updates to the tool and is a good practice.

[gemini-code-assist]

This is a solid pull request template. To make it even more effective and ensure all necessary checks are performed by the author, consider adding a checklist section. This serves as a useful reminder before the PR is submitted for review.

Here's a suggestion for a checklist you could add at the end of the template:

## Checklist

- [ ] I have performed a self-review of my own code.
- [ ] I have commented my code, particularly in hard-to-understand areas.
- [ ] I have made corresponding changes to the documentation.
- [ ] My changes generate no new warnings.
- [ ] I have added tests that prove my fix is effective or that my feature works.
- [ ] New and existing unit tests pass locally with my changes.