ci: add labeler

[ChenZiHong-Gavin]

This PR automates pull request labeling for better repository organization.

[gemini-code-assist]

Summary of Changes

Hello @ChenZiHong-Gavin, 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 integrates a GitHub Action to automate the labeling of pull requests. By defining specific file path patterns in a new configuration file, PRs will automatically receive relevant labels, which will enhance repository organization and streamline the review process by making it easier to identify the scope of changes at a glance.

Highlights

• Automated PR Labeling: This pull request introduces a new GitHub Actions configuration file (.github/labeler.yml) to automatically apply labels to pull requests based on the paths of the files modified. This will help categorize PRs for better organization and review.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/labeler.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 introduces a GitHub Actions labeler configuration to automate PR labeling. The configuration has a critical syntax error that will prevent it from working. I've provided a suggestion to fix the YAML syntax and also to improve the pattern for matching workflow files. With these changes, the labeler should work as intended.

[gemini-code-assist]

The YAML syntax in this file is invalid because list items are not indented under their keys. This will cause the labeler action to fail. I've corrected the indentation and also expanded the workflows pattern to include .yaml files, as GitHub Actions supports both .yml and .yaml extensions.

core:
  - graphgen/**/*

examples:
  - examples/**/*

baselines:
  - baselines/**/*

documentation:
  - "**/*.md"

workflows:
  - .github/workflows/*.yml
  - .github/workflows/*.yaml

config:
  - .github/labeler.yml
  - .pre-commit-config.yaml
  - .pylintrc

[ChenZiHong-Gavin]

/gemini review

[gemini-code-assist]

Code Review

This pull request introduces automated labeling for issues and pull requests, which is a great step for repository organization. The configuration for issue labeling is well-structured, and I've suggested a few additional keywords to enhance its accuracy. For the pull request labeler, I've identified a critical issue in a file path for the configuration files themselves and proposed a fix to ensure changes to the labeler setup are correctly tracked.

[gemini-code-assist]

To improve the accuracy of bug detection, consider adding failure to the list of keywords. It's a common synonym for the existing terms.

  - '\b(bug|error|fail|failure|crash|defect|broken)\b'

[gemini-code-assist]

To better capture enhancement requests, consider adding suggestion to your keyword list. This will help in labeling issues that are phrased as suggestions for improvement.

  - '\b(feature|request|idea|proposal|improve|add|suggestion)\b'

[gemini-code-assist]

To broaden the scope for questions, you could add the keyword assistance. This can help catch requests for help that don't use the other specified terms.

  - '\b(question|help|how to|support|query|assistance)\b'