-
Notifications
You must be signed in to change notification settings - Fork 2
51 lines (49 loc) · 1.91 KB
/
Copy pathpullfrog.yml
File metadata and controls
51 lines (49 loc) · 1.91 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
45
46
47
48
49
50
51
# PULLFROG ACTION — DO NOT EDIT EXCEPT WHERE INDICATED
name: Pullfrog
run-name: ${{ inputs.name || github.workflow }}
on:
workflow_dispatch:
inputs:
prompt:
type: string
description: Agent prompt
name:
type: string
description: Run name
permissions:
contents: read
jobs:
pullfrog:
# Skip runs triggered by bumpy-bot (the automated "Versioned release" PRs on
# bumpy/version-packages). Every push to main refreshes that PR, which would
# otherwise trigger a paid re-review each time. Human-triggered runs on that
# PR (e.g. an @pullfrog mention) still execute, since the triggerer is the human.
if: ${{ !contains(inputs.prompt, '"triggerer":"bumpy-bot"') }}
runs-on: ubuntu-latest
permissions:
id-token: write
contents: read
steps:
- name: Checkout code
uses: actions/checkout@v6
with:
fetch-depth: 1
- name: Run agent
uses: pullfrog/pullfrog@v0
with:
prompt: ${{ inputs.prompt }}
env:
# Review with GPT Sol via our Azure Foundry deployment instead of the
# default Anthropic route. AZURE_API_KEY comes from the Pullfrog
# dashboard; the rest is set here so it stays readable in run logs
# (dashboard-stored values get registered as GitHub Actions log masks).
# Since pullfrog 0.1.58 (first-class Azure support), the deployment
# name and the model's token limits are required: a deployment name
# carries no catalog metadata, so pullfrog cannot look them up, and
# without them completions cap at 32000 tokens and auto-compaction
# is disabled. Limits per models.dev azure/gpt-5.6-sol.
AZURE_RESOURCE_NAME: pullfrog-resource
AZURE_DEPLOYMENT: gpt-5.6-sol
AZURE_CONTEXT: '1050000'
AZURE_MAX_OUTPUT: '128000'
PULLFROG_MODEL: azure/gpt-5.6-sol