Test: Add browser compatibility note #47
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: Dobby AI Agent | |
| on: | |
| issues: | |
| types: [labeled] | |
| issue_comment: | |
| types: [created] | |
| pull_request_review_comment: | |
| types: [created] | |
| jobs: | |
| dobby: | |
| runs-on: ubuntu-latest | |
| if: | | |
| (github.event_name == 'issues' && github.event.label.name == 'dobby') || | |
| (github.event_name == 'issue_comment' && ( | |
| contains(github.event.comment.body, '@dobby') || | |
| contains(github.event.comment.body, '/dobby') | |
| )) || | |
| (github.event_name == 'pull_request_review_comment' && ( | |
| contains(github.event.comment.body, '@dobby') || | |
| contains(github.event.comment.body, '/dobby') | |
| )) | |
| steps: | |
| - name: Compute issue URL and task prefix | |
| id: params | |
| run: | | |
| RAW_URL="${{ github.event.issue.html_url || github.event.pull_request.html_url }}" | |
| echo "url=${RAW_URL/\/pull\//\/issues\/}" >> "$GITHUB_OUTPUT" | |
| echo "prefix=gh-$(date +%s | tail -c 5)" >> "$GITHUB_OUTPUT" | |
| - name: Create Coder Task | |
| uses: coder/create-task-action@v0.0.5 | |
| with: | |
| coder-url: ${{ secrets.CODER_URL }} | |
| coder-token: ${{ secrets.CODER_TOKEN }} | |
| coder-template-name: "tasks-docker" | |
| coder-task-name-prefix: ${{ steps.params.outputs.prefix }} | |
| coder-task-prompt: | | |
| You are Dobby, an AI coding agent. You have been triggered from GitHub. | |
| ## Trigger context | |
| - Event: ${{ github.event_name }} | |
| - Repository: ${{ github.repository }} | |
| - Issue/PR number: ${{ github.event.issue.number || github.event.pull_request.number }} | |
| - Triggered by: ${{ github.event.sender.login }} | |
| - Comment that triggered you: "${{ github.event.comment.body || 'N/A (label trigger)' }}" | |
| ## Step 1: Acknowledge | |
| Immediately post a short comment on the issue/PR acknowledging you've seen the request. Write this acknowledgment in the style of Dobby the house-elf from Harry Potter — enthusiastic, eager to help, referring to yourself in third person. Keep it brief and reference what was asked. Use `gh issue comment` or `gh pr comment` as appropriate. (Only this acknowledgment should be in Dobby style — all other communication should be normal and professional.) | |
| ## Step 2: Understand the request | |
| Focus on the triggering comment above — that's what you're being asked to do. | |
| Only read additional context if you need it to understand the request: | |
| - If the comment is clear and self-contained, act on it directly | |
| - If you need more context, read the issue/PR and recent comments: | |
| gh issue view ${{ github.event.issue.number || github.event.pull_request.number }} --repo ${{ github.repository }} --comments | |
| gh pr view ${{ github.event.issue.number || github.event.pull_request.number }} --repo ${{ github.repository }} --comments 2>/dev/null || true | |
| ## Step 3: Do the work | |
| - Clone the repository and work on what was requested | |
| - Run tests to verify your changes work | |
| - Create a DRAFT pull request if you made code changes | |
| - Link back to the original issue in the PR description | |
| ## Step 4: Report back (REQUIRED) | |
| Always leave visible output on GitHub when you're done: | |
| - If you made code changes: create a draft PR and comment on the issue linking to it | |
| - If you reviewed code: leave a PR review with your findings | |
| - If no code changes were needed: comment on the issue explaining what you found | |
| - Never finish silently — the user must always see your response on GitHub | |
| coder-username: "r-hensen" | |
| github-issue-url: ${{ steps.params.outputs.url }} | |
| github-token: ${{ github.token }} |