Skip to content

Commit d125e0a

Browse files
authored
feat: rename triage workflows (#240)
this makes the workflows consistent and concise in naming
1 parent 99fc996 commit d125e0a

4 files changed

Lines changed: 6 additions & 6 deletions

File tree

.github/workflows/gemini-scheduled-triage.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,13 +8,13 @@ on:
88
- 'main'
99
- 'release/**/*'
1010
paths:
11-
- '.github/workflows/gemini-issue-scheduled-triage.yml'
11+
- '.github/workflows/gemini-scheduled-triage.yml'
1212
push:
1313
branches:
1414
- 'main'
1515
- 'release/**/*'
1616
paths:
17-
- '.github/workflows/gemini-issue-scheduled-triage.yml'
17+
- '.github/workflows/gemini-scheduled-triage.yml'
1818
workflow_dispatch:
1919

2020
concurrency:

examples/workflows/issue-triage/README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -57,8 +57,8 @@ To implement this issue triage system, you can utilize either of the following m
5757

5858
```bash
5959
mkdir -p .github/workflows
60-
curl -o .github/workflows/gemini-issue-automated-triage.yml https://raw.githubusercontent.com/google-github-actions/run-gemini-cli/main/examples/workflows/issue-triage/gemini-issue-automated-triage.yml
61-
curl -o .github/workflows/gemini-issue-scheduled-triage.yml https://raw.githubusercontent.com/google-github-actions/run-gemini-cli/main/examples/workflows/issue-triage/gemini-issue-scheduled-triage.yml
60+
curl -o .github/workflows/gemini-triage.yml https://raw.githubusercontent.com/google-github-actions/run-gemini-cli/main/examples/workflows/issue-triage/gemini-triage.yml
61+
curl -o .github/workflows/gemini-scheduled-triage.yml https://raw.githubusercontent.com/google-github-actions/run-gemini-cli/main/examples/workflows/issue-triage/gemini-scheduled-triage.yml
6262
```
6363

6464
You can customize the prompts and settings in the workflow files to suit your specific needs. For example, you can change the triage logic, the labels that are applied, or the schedule of the scheduled triage.
@@ -76,13 +76,13 @@ The Issue Triage workflows are triggered by:
7676

7777
### Real-Time Issue Triage
7878

79-
This workflow is defined in `workflows/issue-triage/gemini-issue-automated-triage.yml` and is triggered when an issue is opened or reopened. It uses the Gemini CLI to analyze the issue and apply relevant labels.
79+
This workflow is defined in `workflows/issue-triage/gemini-triage.yml` and is triggered when an issue is opened or reopened. It uses the Gemini CLI to analyze the issue and apply relevant labels.
8080

8181
If the triage process encounters an error, the workflow will post a comment on the issue, including a link to the action logs for debugging.
8282

8383
### Scheduled Issue Triage
8484

85-
This workflow is defined in `workflows/issue-triage/gemini-issue-scheduled-triage.yml` and runs on a schedule (e.g., every hour). It finds any issues that have no labels or have the `status/needs-triage` label and then uses the Gemini CLI to triage them. This workflow can also be manually triggered.
85+
This workflow is defined in `workflows/issue-triage/gemini-scheduled-triage.yml` and runs on a schedule (e.g., every hour). It finds any issues that have no labels or have the `status/needs-triage` label and then uses the Gemini CLI to triage them. This workflow can also be manually triggered.
8686

8787
### Manual Triage
8888

examples/workflows/issue-triage/gemini-issue-scheduled-triage.yml renamed to examples/workflows/issue-triage/gemini-scheduled-triage.yml

File renamed without changes.

examples/workflows/issue-triage/gemini-issue-automated-triage.yml renamed to examples/workflows/issue-triage/gemini-triage.yml

File renamed without changes.

0 commit comments

Comments
 (0)