chore: import upstream snapshot with attribution
Docker Image CI / build-ubuntu2004 (push) Has been cancelled
Docker Image CI / build-ubuntu2004 (push) Has been cancelled
This commit is contained in:
@@ -0,0 +1,46 @@
|
||||
name: Label New Issues
|
||||
|
||||
on:
|
||||
issues:
|
||||
types: [opened]
|
||||
|
||||
permissions:
|
||||
issues: write
|
||||
contents: read
|
||||
|
||||
jobs:
|
||||
label-issue:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- name: Checkout private action repository
|
||||
uses: actions/checkout@v4
|
||||
with:
|
||||
repository: NVIDIA/goggles_action
|
||||
path: ./.github/actions/goggles_action # local path to store the action
|
||||
ref: v1.3.0
|
||||
|
||||
- name: AI Label Issue
|
||||
uses: ./.github/actions/goggles_action/actions/llm_label
|
||||
with:
|
||||
ACTION_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
||||
LLM_MODEL_NAME: ${{ secrets.LLM_MODEL_NAME }}
|
||||
LLM_TOKEN_SERVER_URL: ${{ secrets.LLM_TOKEN_SERVER_URL }}
|
||||
LLM_TOKEN_CLIENT_ID: ${{ secrets.LLM_TOKEN_CLIENT_ID }}
|
||||
LLM_TOKEN_CLIENT_SECRET: ${{ secrets.LLM_TOKEN_CLIENT_SECRET }}
|
||||
LLM_GENERATE_URL: ${{ secrets.LLM_GENERATE_URL }}
|
||||
LLM_TOKEN_SCOPE: ${{ secrets.LLM_TOKEN_SCOPE }}
|
||||
REPO_OWNER: ${{ github.repository_owner }}
|
||||
REPO_NAME: ${{ github.event.repository.name }}
|
||||
ISSUE_NUMBER: ${{ github.event.issue.number }}
|
||||
ISSUE_TITLE: ${{ github.event.issue.title }}
|
||||
ISSUE_BODY: ${{ github.event.issue.body }}
|
||||
GITHUB_API_URL: ${{ github.api_url }}
|
||||
ACTIONS_STEP_VERBOSE: false
|
||||
EXCLUDED_LABELS: "Investigating,internal-bug-tracked,stale,triaged,wontfix"
|
||||
LLM_SYSTEM_PROMPT: |
|
||||
You are an expert GitHub issue labeler. Your task is to analyze the provided issue title, issue body, and a list of available labels with their descriptions.
|
||||
Based on this information, select the single most appropriate label from the list that best captures the primary issue or request.
|
||||
Prefer selecting only one label that represents the main topic or problem. Only suggest multiple labels if the issue genuinely spans multiple distinct areas that are equally important.
|
||||
Respond with ONLY the chosen label name (e.g., 'bug', 'feature-request') or comma-separated names if multiple are truly needed.
|
||||
If no labels seem appropriate, respond with 'NONE'.
|
||||
Do not add any other text, explanation, or markdown formatting.
|
||||
Reference in New Issue
Block a user