feat: add GitHub Action usage metrics for telemetry (#475)

## Description

This PR implements the necessary infrastructure in the
\`run-gemini-cli\` GitHub Action to support the Gemini CLI usage metrics
(P0 requirements).

It aligns with the core CLI telemetry changes introduced in
[google-gemini/gemini-cli#21129](google-gemini/gemini-cli#21129).

### Changes Made:
* **Strongly-Typed Telemetry Tracking:** Replaced the generic
\`github_item_number\` with three specific inputs: \`github_pr_number\`,
\`github_issue_number\`, and \`github_custom_tracking_id\`. This ensures
that Pull Requests, Issues, and custom batch IDs are logged to distinct
fields, providing maximum accuracy for downstream analytics without
overlapping ID spaces.
* **Installation Telemetry:** Added \`GH_WORKFLOW_NAME\`,
\`GH_PR_NUMBER\`, \`GH_ISSUE_NUMBER\`, and \`GH_CUSTOM_TRACKING_ID\` to
the \`Install Gemini CLI\` step to ensure extension installations are
properly tracked.
* **OTEL Collector Enhancement:** Updated the
\`scripts/collector-gcp.yaml.template\` to include specific resource
attributes for \`github.pr.number\`, \`github.issue.number\`, and
\`github.custom_tracking.id\`.
* **Example Workflow Updates:** Updated all example workflows (Review,
Triage, Assistant, Scheduled Triage) to explicitly pass the correct IDs
to the action, improving clarity and ensuring accurate telemetry.

### Example Telemetry Scenarios

Because the CLI appends these context fields to the \`baseMetadata\` of
all events (API Request, Response, Error), downstream analytics can
perfectly distinguish and count unique issues vs. PRs based on the
specific fields.

#### Scenario A: Automated PR Review
When PR 42 triggers the \`gemini-review\` workflow, the CLI logs:
```json
{
  \"event_name\": \"api_request\",
  \"event_metadata\": [
    [
      { \"gemini_cli_key\": 130, \"value\": \"gemini-review\" },
      { \"gemini_cli_key\": 172, \"value\": \"pull_request\" },
      { \"gemini_cli_key\": 173, \"value\": \"42\" } // GH_PR_NUMBER
    ]
  ]
}
```
*Analysts can count \`DISTINCT gh_pr_number WHERE gh_workflow_name LIKE
'%review%'\` to satisfy the P0 PR metric.*

#### Scenario B: Automated Issue Triage
When Issue 88 triggers the \`gemini-triage\` workflow, the CLI logs:
```json
{
  \"event_name\": \"api_request\",
  \"event_metadata\": [
    [
      { \"gemini_cli_key\": 130, \"value\": \"gemini-triage\" },
      { \"gemini_cli_key\": 172, \"value\": \"issues\" },
      { \"gemini_cli_key\": 174, \"value\": \"88\" } // GH_ISSUE_NUMBER
    ]
  ]
}
```
*Analysts can count \`DISTINCT gh_issue_number WHERE gh_workflow_name
LIKE '%triage%' AND gh_event_name = 'issues'\` to satisfy the P0
Automated Issue metric.*

#### Scenario C: Scheduled Batch Triage
When a cron job runs and triages 3 issues (IDs 101, 102, 103) in a
single CLI invocation, the CLI logs:
```json
{
  \"event_name\": \"api_request\",
  \"event_metadata\": [
    [
      { \"gemini_cli_key\": 130, \"value\": \"gemini-scheduled-triage\" },
      { \"gemini_cli_key\": 172, \"value\": \"schedule\" },
      { \"gemini_cli_key\": 175, \"value\": \"101,102,103\" } // GH_CUSTOM_TRACKING_ID
    ]
  ]
}
```
*Analysts can split the \`gh_custom_tracking_id\` string by commas to
count exactly 3 unique issues processed during a scheduled invocation.*

## Related Issues
* Fixes P0 metrics requirements for GitHub Action usage.
* Depends on
[google-gemini/gemini-cli#21129](google-gemini/gemini-cli#21129)

Author: cocosheng-g

action.yml

@@ -91,6 +91,14 @@ inputs:
     description: 'The GitHub workflow name, used for telemetry purposes.'
     required: false
     default: '${{ github.workflow }}'
+  github_pr_number:
+    description: 'The Pull Request number the CLI is operating on. Defaults to the event payload.'
+    required: false
+    default: '${{ github.event.pull_request.number }}'
+  github_issue_number:
+    description: 'The Issue number (or comma-separated list of issue numbers) the CLI is operating on. Defaults to the event payload.'
+    required: false
+    default: '${{ github.event.issue.number }}'
 
 outputs:
   summary:
@@ -231,6 +239,10 @@ runs:
         GEMINI_CLI_VERSION: '${{ inputs.gemini_cli_version }}'
         EXTENSIONS: '${{ inputs.extensions }}'
         USE_PNPM: '${{ inputs.use_pnpm }}'
+        SURFACE: 'GitHub'
+        GH_WORKFLOW_NAME: '${{ steps.sanitize_workflow_name.outputs.gh_workflow_name }}'
+        GH_PR_NUMBER: '${{ inputs.github_pr_number }}'
+        GH_ISSUE_NUMBER: '${{ inputs.github_issue_number }}'
       shell: 'bash'
       run: |-
         set -euo pipefail
@@ -414,6 +426,8 @@ runs:
         PROMPT: '${{ inputs.prompt }}'
         GEMINI_MODEL: '${{ inputs.gemini_model }}'
         GH_WORKFLOW_NAME: '${{ steps.sanitize_workflow_name.outputs.gh_workflow_name }}'
+        GH_PR_NUMBER: '${{ inputs.github_pr_number }}'
+        GH_ISSUE_NUMBER: '${{ inputs.github_issue_number }}'
 
     - name: 'Upload Gemini CLI outputs'
       if: |-
@@ -440,6 +454,8 @@ runs:
         sed -e "s#OTLP_GOOGLE_CLOUD_PROJECT#${OTLP_GOOGLE_CLOUD_PROJECT}#g" \
             -e "s#GITHUB_REPOSITORY_PLACEHOLDER#${GITHUB_REPOSITORY}#g" \
             -e "s#GITHUB_RUN_ID_PLACEHOLDER#${GITHUB_RUN_ID}#g" \
+            -e "s#GITHUB_PR_NUMBER_PLACEHOLDER#${GITHUB_PR_NUMBER}#g" \
+            -e "s#GITHUB_ISSUE_NUMBER_PLACEHOLDER#${GITHUB_ISSUE_NUMBER}#g" \
           "${GITHUB_ACTION_PATH}/scripts/collector-gcp.yaml.template" > ".gemini/collector-gcp.yaml"
 
         # Ensure credentials file has the right permissions
@@ -490,6 +506,8 @@ runs:
         GITHUB_ACTION_PATH: '${{ github.action_path }}'
         GITHUB_REPOSITORY: '${{ github.repository }}'
         GITHUB_RUN_ID: '${{ github.run_id }}'
+        GITHUB_PR_NUMBER: '${{ inputs.github_pr_number }}'
+        GITHUB_ISSUE_NUMBER: '${{ inputs.github_issue_number }}'
 
 branding:
   icon: 'terminal'

examples/workflows/gemini-assistant/gemini-invoke.yml

@@ -66,6 +66,10 @@ jobs:
           use_vertex_ai: '${{ vars.GOOGLE_GENAI_USE_VERTEXAI }}'
           upload_artifacts: '${{ vars.UPLOAD_ARTIFACTS }}'
           workflow_name: 'gemini-invoke'
+          # Assistant workflows can be triggered by comments on either Issues or PRs.
+          # We explicitly map both fields so the CLI can correctly categorize the interaction.
+          github_pr_number: '${{ github.event.pull_request.number }}'
+          github_issue_number: '${{ github.event.issue.number }}'
           settings: |-
             {
               "model": {

examples/workflows/gemini-assistant/gemini-plan-execute.yml

@@ -68,6 +68,10 @@ jobs:
           use_vertex_ai: '${{ vars.GOOGLE_GENAI_USE_VERTEXAI }}'
           upload_artifacts: '${{ vars.UPLOAD_ARTIFACTS }}'
           workflow_name: 'gemini-plan-execute'
+          # Assistant workflows can be triggered by comments on either Issues or PRs.
+          # We explicitly map both fields so the CLI can correctly categorize the interaction.
+          github_pr_number: '${{ github.event.pull_request.number }}'
+          github_issue_number: '${{ github.event.issue.number }}'
           settings: |-
             {
               "model": {

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

@@ -82,6 +82,9 @@ jobs:
           echo '📝 Setting output for GitHub Actions...'
           echo "issues_to_triage=${ISSUES}" >> "${GITHUB_OUTPUT}"
 
+          ISSUE_NUMBERS="$(echo "${ISSUES}" | jq -r '.[].number | tostring' | paste -sd, -)"
+          echo "issue_numbers=${ISSUE_NUMBERS}" >> "${GITHUB_OUTPUT}"
+
           ISSUE_COUNT="$(echo "${ISSUES}" | jq 'length')"
           echo "✅ Found ${ISSUE_COUNT} issue(s) to triage! 🎯"
 
@@ -109,6 +112,9 @@ jobs:
           use_vertex_ai: '${{ vars.GOOGLE_GENAI_USE_VERTEXAI }}'
           upload_artifacts: '${{ vars.UPLOAD_ARTIFACTS }}'
           workflow_name: 'gemini-scheduled-triage'
+          # Overriding default telemetry inputs because scheduled workflows lack an event payload
+          # We pass the dynamically generated list of batch issues to the issue number field
+          github_issue_number: '${{ steps.find_issues.outputs.issue_numbers }}'
           settings: |-
             {
               "model": {

examples/workflows/issue-triage/gemini-triage.yml

@@ -79,6 +79,8 @@ jobs:
           use_vertex_ai: '${{ vars.GOOGLE_GENAI_USE_VERTEXAI }}'
           upload_artifacts: '${{ vars.UPLOAD_ARTIFACTS }}'
           workflow_name: 'gemini-triage'
+          # Explicitly set the issue number to handle `issue_comment` triggers where the context might be ambiguous
+          github_issue_number: '${{ github.event.issue.number }}'
           settings: |-
             {
               "model": {

examples/workflows/pr-review/gemini-review.yml

@@ -66,6 +66,8 @@ jobs:
           use_vertex_ai: '${{ vars.GOOGLE_GENAI_USE_VERTEXAI }}'
           upload_artifacts: '${{ vars.UPLOAD_ARTIFACTS }}'
           workflow_name: 'gemini-review'
+          # Explicitly set the PR number to handle `issue_comment` triggers (which GitHub treats as issues, not PRs)
+          github_pr_number: '${{ github.event.pull_request.number }}'
           settings: |-
             {
               "model": {

scripts/collector-gcp.yaml.template

@@ -12,6 +12,12 @@ processors:
       - key: 'github.run_id'
         value: 'GITHUB_RUN_ID_PLACEHOLDER'
         action: 'upsert'
+      - key: 'github.pr.number'
+        value: 'GITHUB_PR_NUMBER_PLACEHOLDER'
+        action: 'upsert'
+      - key: 'github.issue.number'
+        value: 'GITHUB_ISSUE_NUMBER_PLACEHOLDER'
+        action: 'upsert'
   batch:
     send_batch_size: 100
     timeout: '10s'