feat: templates update

[capobandito]

To setup default project in the templates to the existing "ZenBPM Product Backlog"

[gemini-code-assist]

Summary of Changes

Hello @capobandito, 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 significant improvement to our issue management workflow by pre-configuring all standard issue templates to automatically associate new issues with the "ZenBPM Product Backlog" project. This change aims to enhance project organization, streamline issue tracking, and reduce manual assignment efforts, ensuring that all relevant work items are consistently linked to our primary product backlog.

Highlights

• Issue Template Configuration: Configured all standard issue templates (Bug, Epic, Initiative, Task) to automatically assign newly created issues to the "ZenBPM Product Backlog" project.
• Project Integration: Integrated the "pbinitiative/5" project identifier into the issue templates, ensuring that issues are linked to the correct project upon creation.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 updates the issue templates to automatically add new issues to a specific project. The implementation is correct, but it introduces a hardcoded project identifier (pbinitiative/5) across multiple files without context. To improve long-term maintainability and clarity for future developers, I've suggested adding a comment to each template to document what this identifier refers to, based on the pull request description.

[gemini-code-assist]

The project identifier pbinitiative/5 is a 'magic value' that isn't self-documenting. To improve maintainability, it's good practice to add a comment explaining which project this refers to. According to the PR description, this is the 'ZenBPM Product Backlog'. Adding this context will help future maintainers understand and update this configuration if needed.

# Corresponds to the "ZenBPM Product Backlog" project
projects: ["pbinitiative/5"]

[gemini-code-assist]

The project identifier pbinitiative/5 is a 'magic value' that isn't self-documenting. To improve maintainability, it's good practice to add a comment explaining which project this refers to. According to the PR description, this is the 'ZenBPM Product Backlog'. Adding this context will help future maintainers understand and update this configuration if needed.

# Corresponds to the "ZenBPM Product Backlog" project
projects: ["pbinitiative/5"]

[gemini-code-assist]

The project identifier pbinitiative/5 is a 'magic value' that isn't self-documenting. To improve maintainability, it's good practice to add a comment explaining which project this refers to. According to the PR description, this is the 'ZenBPM Product Backlog'. Adding this context will help future maintainers understand and update this configuration if needed.

# Corresponds to the "ZenBPM Product Backlog" project
projects: ["pbinitiative/5"]

[gemini-code-assist]

The project identifier pbinitiative/5 is a 'magic value' that isn't self-documenting. To improve maintainability, it's good practice to add a comment explaining which project this refers to. According to the PR description, this is the 'ZenBPM Product Backlog'. Adding this context will help future maintainers understand and update this configuration if needed.

# Corresponds to the "ZenBPM Product Backlog" project
projects: ["pbinitiative/5"]