feat(examples): add automated issue cleanup workflow#498
Open
cocosheng-g wants to merge 32 commits intomainfrom
Open
feat(examples): add automated issue cleanup workflow#498cocosheng-g wants to merge 32 commits intomainfrom
cocosheng-g wants to merge 32 commits intomainfrom
Conversation
Adds a new GitHub Action workflow and Gemini CLI command configuration to automatically process open issues with specific labels. The workflow identifies the 10 issues with the oldest last update time, checks their validity against the codebase, searches for duplicates, and provides a triage summary (Maintainer-only vs Help-wanted) for further review.
Contributor
|
🤖 Hi @cocosheng-g, I've received your request, and I'm working on it now! You can track my progress in the logs for more details. |
![gemini-cli[bot]](https://avatars.githubusercontent.com/in/1473539?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
This PR introduces a well-structured example workflow for automated issue cleanup using the Gemini CLI. The logic for checking validity, finding duplicates, and providing triage summaries is clear and provides a great template for repository maintainers.
🔍 General Feedback
- Improve Reusability: The primary feedback is to reduce hardcoded repository names in both the workflow and TOML configuration. By using
${{ github.repository }}and passing it as an environment variable, the example becomes significantly easier for users to adopt in their own projects. - Workflow Consistency: The use of
run_shell_command(gh)is consistent with existing examples in the repository. - Small Synchronizations: There is a minor mismatch between a comment and the code regarding JSON data types in the issue fetching step.
… instructions are omitted
cocosheng-g
force-pushed
the
feat/issue-cleanup-workflow
branch
from
0dd8182 to
cf62bef
Compare
cocosheng-g
force-pushed
the
feat/issue-cleanup-workflow
branch
from
f3992b6 to
1cdeb18
Compare
…o verify bug fixes
…requests tracked by projects
…and remove project tracking skip
…sues before handling 30-day inactivity
… self-investigation
… and advanced triage logic
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces a new example workflow for automated issue cleanup.
Description
The
gemini-issue-cleanupworkflow runs on a weekly schedule (or manually) to target 10 specific open issues with the oldest last update time. For each issue, the Gemini CLI analyzes the current repository state to:Maintainer-onlyorHelp-wanted.Changes Made
examples/workflows/issue-cleanup/gemini-issue-cleanup.ymlexamples/workflows/issue-cleanup/gemini-issue-cleanup.tomlexamples/workflows/issue-cleanup/README.md