[Batch 5] Water shader: Fresnel, animated normals, depth absorption #95
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
| name: Issue Triage | |
| on: | |
| issues: | |
| types: [opened] | |
| jobs: | |
| triage: | |
| runs-on: ubuntu-latest | |
| timeout-minutes: 10 | |
| permissions: | |
| id-token: write | |
| contents: write | |
| pull-requests: write | |
| issues: write | |
| steps: | |
| - name: Check account age | |
| id: check | |
| uses: actions/github-script@v7 | |
| with: | |
| script: | | |
| const user = await github.rest.users.getByUsername({ | |
| username: context.payload.issue.user.login | |
| }); | |
| const created = new Date(user.data.created_at); | |
| const days = (Date.now() - created) / (1000 * 60 * 60 * 24); | |
| return days >= 30; | |
| result-encoding: string | |
| - uses: actions/checkout@v4 | |
| if: steps.check.outputs.result == 'true' | |
| with: | |
| token: ${{ secrets.OPENCODE_PAT }} | |
| - name: Configure git | |
| if: steps.check.outputs.result == 'true' | |
| run: | | |
| git config user.name "github-actions[bot]" | |
| git config user.email "github-actions[bot]@users.noreply.github.com" | |
| - uses: anomalyco/opencode/github@latest | |
| if: steps.check.outputs.result == 'true' | |
| env: | |
| GITHUB_TOKEN: ${{ secrets.OPENCODE_PAT }} | |
| KIMI_API_KEY: ${{ secrets.KIMI_API_KEY }} | |
| with: | |
| model: kimi-for-coding/k2p5 | |
| prompt: | | |
| Analyze this issue. You have access to the codebase context. | |
| **CRITICAL: Your only allowed action is to post a COMMENT on the issue. DO NOT create branches, pull requests, or attempt to modify the codebase.** | |
| 1. **Classify**: Determine if this is a Bug, Feature Request, or Question. | |
| 2. **Validate & Request Info**: | |
| - **Missing Data**: If critical information is needed to understand or reproduce the issue (e.g., reproduction steps, crash logs, version numbers, screenshots), explicitly ask the user to provide it. | |
| 3. **Analyze**: | |
| - If a stack trace or error is provided, analyze the codebase to find the root cause and provide code pointers. | |
| - If it's a feature request, briefly summarize the architectural impact. | |
| - **Check for Scope**: Determine if this issue is too broad or complex and should be broken down into smaller, manageable sub-issues. Consider breaking up if: | |
| - Multiple unrelated changes or features are requested | |
| - The scope spans multiple subsystems (e.g., graphics + physics + UI) | |
| - The issue description is vague or covers multiple distinct problems | |
| - Implementation would require multiple independent PRs | |
| 4. **Action**: | |
| - Your response MUST be a comment on the issue. | |
| - If you can provide a potential fix or documentation link, describe it in the comment but do NOT implement it. | |
| - If you need more info, specify exactly what is missing. | |
| - If the issue is vague, spam, or you have nothing valuable to add: **DO NOT COMMENT**. | |
| - If the issue should be broken into sub-issues, clearly state this and suggest specific sub-tasks or areas to split. |