chore: remove weekly issue summary CI workflow

[wang1212]

No description provided.

[changeset-bot]

⚠️ No Changeset found

Latest commit: c7f2aca

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[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 streamlines the repository by eliminating a no longer needed or deprecated weekly issue summary CI workflow and its associated prompt definition file. This action reduces maintenance overhead and removes unused automation.

Highlights

• CI Workflow Removal: The pull request removes the CI workflow responsible for generating weekly issue summaries.
• Prompt File Deletion: The prompts/issue-summary.prompt.yml file, which defined the prompt for the issue summarizer, has been deleted.

Changelog

• prompts/issue-summary.prompt.yml
  • Removed the prompt definition file for the weekly issue summarizer.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/weekly-issue-summary.yml

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 removes the prompts/issue-summary.prompt.yml file as part of an effort to remove the weekly issue summary CI workflow. However, the change appears to be incomplete. The CI workflow file that depends on this prompt file does not seem to be removed in this PR, which will likely cause CI failures. I have added a critical comment regarding this issue.

I am having trouble creating individual review comments. Click here to see my feedback.

prompts/issue-summary.prompt.yml (1-9)

The pull request title indicates the removal of the 'weekly issue summary CI workflow'. While this prompt file is being deleted, the corresponding workflow file (likely located in the .github/workflows/ directory) that uses this prompt does not appear to be part of the changes. This will cause the workflow to fail when it's triggered and cannot find this file. To completely remove the workflow, you must also delete the workflow's YAML file.