-
Notifications
You must be signed in to change notification settings - Fork 32
Expand file tree
/
Copy pathrespond-to-comment.yml
More file actions
42 lines (41 loc) · 1.45 KB
/
respond-to-comment.yml
File metadata and controls
42 lines (41 loc) · 1.45 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
# Template workflow generated from examples/respond-to-comment.yml.
# Copy this file into .github/workflows/ in your own repository and customize as needed.
# Do not edit this file in-place in this repo; instead, edit the source example and run:
# npm run gen-workflows
# ======================================================================================
# Workflow: Respond to Comment
# ======================================================================================
# Usage:
# - Comment on a PR or Issue with "@oz-agent".
# - You can ask questions or request code changes (e.g., "@oz-agent fix this typo").
#
# Setup:
# - Ensure WARP_API_KEY is set in Repository Secrets.
#
# Expected Output:
# - The Agent replies to your comment with an answer or confirmation.
# - If code changes were requested, the Agent commits them directly to the PR branch.
#
# When to use:
# - Use this for interactive coding assistance during code review or issue triage.
# ======================================================================================
name: Respond to Comment
on:
issue_comment:
types:
- created
pull_request_review_comment:
types:
- created
jobs:
respond:
uses: warpdotdev/oz-agent-action/.github/workflows/respond-to-comment.yml@v1
with:
# These inputs are all optional
profile: ''
model: ''
name: ''
mcp: ''
skill: ''
secrets:
WARP_API_KEY: ${{ secrets.WARP_API_KEY }}