-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathforge.yml
More file actions
44 lines (39 loc) · 1.6 KB
/
Copy pathforge.yml
File metadata and controls
44 lines (39 loc) · 1.6 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
43
44
# Copy this file to .github/workflows/forge.yml in your repository.
# Minimal ShipIT Forge setup — same shape as Claude Code's example workflow.
name: ShipIT Forge
on:
issues:
types: [opened, labeled]
issue_comment:
types: [created]
pull_request:
types: [opened, synchronize, review_requested]
pull_request_review_comment:
types: [created]
permissions:
contents: write # edit code, push fix branches
issues: write # read issues, post comments
pull-requests: write # open PRs, post reviews + inline comments
checks: read # read CI check results
statuses: read # read commit statuses
actions: write # read logs + re-run failed workflows (CI auto-fix)
# NOTE: GITHUB_TOKEN cannot push changes to .github/workflows/** by design.
# If a fix must edit a workflow file, run the hosted App (APP_ID/PRIVATE_KEY below),
# whose App permission `workflows: write` allows it.
jobs:
forge:
runs-on: ubuntu-latest
steps:
- uses: shipiit/forge@v1
with:
provider: anthropic
env:
# Pick ONE provider and set its key as a repo/org secret.
ANTHROPIC_API_KEY: ${{ secrets.ANTHROPIC_API_KEY }}
# OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
# LLM_PROVIDER: vertex
# VERTEX_PROJECT: ${{ vars.VERTEX_PROJECT }}
# VERTEX_CREDENTIALS_JSON: ${{ secrets.VERTEX_SA_JSON }}
# OPTIONAL — act as your installed GitHub App (bot identity), like Claude's app:
# APP_ID: ${{ secrets.FORGE_APP_ID }}
# PRIVATE_KEY: ${{ secrets.FORGE_APP_PRIVATE_KEY }}