Repository navigation
chore: initialize fullsend per-repo installation #12721
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,28 @@ | ||
| # fullsend per-repo configuration | ||
| # https://github.com/fullsend-ai/fullsend | ||
| # | ||
| # This file configures fullsend for per-repo installation mode. | ||
| # See https://fullsend.sh/docs/guides/infrastructure/layered-config-reference | ||
| version: "1" | ||
| tracker: | ||
| github: | ||
| allowed_targets: | ||
| repos: | ||
| - fullsend-ai/fullsend | ||
| - fullsend-ai/agents | ||
| runtime: pi | ||
| roles: | ||
| - review | ||
| agents: | ||
| - name: review | ||
| model: google-vertex/gemini-3.8-flash | ||
| - name: retro | ||
| enabled: false | ||
| - name: prioritize | ||
| enabled: false | ||
|
dlabaj marked this conversation as resolved.
Resolved
|
||
| allowed_remote_resources: | ||
| - https://raw.githubusercontent.com/fullsend-ai/fullsend/ | ||
| - https://raw.githubusercontent.com/fullsend-ai/agents/ | ||
| inference: | ||
| project: firefly-868139 | ||
| wif_provider: projects/275116376890/locations/global/workloadIdentityPools/uie-github-fullsend-inference/providers/gh-repo-84372347 | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,141 @@ | ||
| # This file is managed by fullsend. Do not edit it directly. | ||
| # Upstream: https://github.com/fullsend-ai/fullsend/blob/main/internal/scaffold/fullsend-repo/.github/workflows/fullsend.yaml | ||
| --- | ||
| # fullsend shim workflow (per-repo installation mode) | ||
| # Routes events to agent workflows via reusable-dispatch.yml. | ||
| # All agent execution happens in this repository's context. | ||
| # | ||
| # Security: pull_request_target runs the BASE branch version of this workflow, | ||
| # preventing PRs from modifying it to exfiltrate credentials. | ||
| # This shim never checks out PR code, so it is not vulnerable to "pwn request" | ||
| # attacks. | ||
| # | ||
| # Routing: this shim forwards the raw event context to reusable-dispatch.yml, | ||
| # which determines the stage and runs the agent inline (ADR 62). | ||
| # Adding a new stage requires only a job in reusable-dispatch.yml — zero changes to this repo. | ||
| # | ||
| # Concurrency: per-role cancel-in-progress groups live in reusable-dispatch.yml | ||
| # stage jobs with -agent- suffix. Roles operate independently (#2452). | ||
| name: fullsend | ||
|
|
||
| on: | ||
| issues: | ||
| types: [opened, edited, labeled] | ||
| issue_comment: | ||
| types: [created] | ||
| pull_request_target: | ||
| types: [opened, synchronize, ready_for_review, closed, labeled, unlabeled] | ||
| pull_request_review: | ||
| types: [submitted] | ||
|
|
||
| permissions: {} | ||
|
|
||
| jobs: | ||
| dispatch: | ||
| if: >- | ||
| (github.event_name != 'pull_request_target' && github.event_name != 'pull_request_review' | ||
| || github.event.pull_request.head.ref != 'fullsend/scaffold-install') | ||
| && (github.event_name != 'issue_comment' | ||
| || startsWith(github.event.comment.body, '/fs-')) | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Differs slightly from chatbot workflow |
||
| permissions: | ||
| actions: write | ||
| id-token: write | ||
| contents: write | ||
| issues: write | ||
| packages: read | ||
| pull-requests: write | ||
| uses: fullsend-ai/fullsend/.github/workflows/reusable-dispatch.yml@v0.56.1 | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Pins 0.56.1 over 0.52.0 |
||
| with: | ||
| event_action: ${{ github.event.action }} | ||
| mint_url: ${{ vars.FULLSEND_MINT_URL }} | ||
| gcp_region: ${{ vars.FULLSEND_GCP_REGION }} | ||
| project_number: ${{ vars.FULLSEND_PROJECT_NUMBER }} | ||
| runner_image: ubuntu-24.04 | ||
| secrets: | ||
| FULLSEND_GCP_WIF_PROVIDER: ${{ secrets.FULLSEND_GCP_WIF_PROVIDER }} | ||
| FULLSEND_GCP_PROJECT_ID: ${{ secrets.FULLSEND_GCP_PROJECT_ID }} | ||
| FULLSEND_OPENAI_API_KEY: ${{ secrets.FULLSEND_OPENAI_API_KEY }} | ||
| FULLSEND_INFERENCE_GATEWAY_API_KEY: ${{ secrets.FULLSEND_INFERENCE_GATEWAY_API_KEY }} | ||
| OTEL_EXPORTER_OTLP_TRACES_HEADERS: ${{ secrets.OTEL_EXPORTER_OTLP_TRACES_HEADERS }} | ||
| OTEL_EXPORTER_OTLP_HEADERS: ${{ secrets.OTEL_EXPORTER_OTLP_HEADERS }} | ||
| FULLSEND_JIRA_TOKEN: ${{ secrets.FULLSEND_JIRA_TOKEN }} | ||
| FULLSEND_JIRA_EMAIL: ${{ secrets.FULLSEND_JIRA_EMAIL }} | ||
| FULLSEND_JIRA_CLIENT_ID: ${{ secrets.FULLSEND_JIRA_CLIENT_ID }} | ||
| FULLSEND_JIRA_CLIENT_SECRET: ${{ secrets.FULLSEND_JIRA_CLIENT_SECRET }} | ||
|
Comment on lines
+61
to
+64
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. These secrets weren't logged in the dry run and shouldn't exist yet, not sure why they were added in the normal run. Should I remove them? |
||
| FULLSEND_GITHUB_RUNNER_SECRETS: ${{ secrets.FULLSEND_GITHUB_RUNNER_SECRETS }} | ||
|
|
||
| stop-fix: | ||
| # Job-level if: is intentionally coarse — it only screens for the | ||
| # /fs-fix-stop command on a PR from a non-bot. The authoritative | ||
| # authorization decision (collaborator permission API + PR-author escape | ||
| # hatch) is made in the step below, so a maintainer whose author_association | ||
| # is not MEMBER (e.g. private org membership) is not filtered out (ADR 0054). | ||
| if: >- | ||
| github.event_name == 'issue_comment' | ||
| && github.event.issue.pull_request | ||
| && github.event.comment.user.type != 'Bot' | ||
| && github.event.comment.body == '/fs-fix-stop' | ||
| runs-on: ubuntu-24.04 | ||
| permissions: | ||
| contents: read | ||
| issues: write | ||
| pull-requests: write | ||
| steps: | ||
| - name: Add fullsend-no-fix label and notify | ||
| env: | ||
| GH_TOKEN: ${{ github.token }} | ||
| PR_NUMBER: ${{ github.event.issue.number }} | ||
| REPO: ${{ github.repository }} | ||
| COMMENT_USER_LOGIN: ${{ github.event.comment.user.login }} | ||
| ISSUE_USER_LOGIN: ${{ github.event.issue.user.login }} | ||
| run: | | ||
| set -euo pipefail | ||
| # ADR 0054: authorize via the collaborator permission API | ||
| # (admin|maintain|write), not author_association — the latter grants | ||
| # contributor status to anyone with a single merged PR (issue #5421). | ||
| # Mirrors has_repo_permission() in reusable-dispatch.yml, including the | ||
| # custom-role --jq resolution; keep the two in sync. | ||
| # The PR author may always stop the fix agent on their own PR. | ||
| authorized=false | ||
| if [[ -n "$COMMENT_USER_LOGIN" && "$COMMENT_USER_LOGIN" == "$ISSUE_USER_LOGIN" ]]; then | ||
| authorized=true | ||
| else | ||
| if api_err=$(mktemp); then | ||
| # $p is a jq variable; the single quotes are intentional. | ||
| # shellcheck disable=SC2016 | ||
| if role=$(gh api "repos/$REPO/collaborators/$COMMENT_USER_LOGIN/permission" \ | ||
| --jq '.user.permissions as $p | ||
| | if (.role_name | type) != "string" or .role_name == "" then "none" | ||
| elif (.role_name | IN("admin", "maintain", "write", "triage", "read")) then .role_name | ||
| elif $p == null then | ||
| if (.permission | IN("admin", "write", "read")) then .permission else "none" end | ||
| elif ($p | type) == "object" then | ||
| if $p.admin == true then "admin" | ||
| elif $p.maintain == true then "maintain" | ||
| elif $p.push == true then "write" | ||
| elif $p.triage == true then "triage" | ||
| elif $p.pull == true then "read" | ||
| else "none" end | ||
| else "none" end' 2>"$api_err"); then | ||
| case "$role" in | ||
| admin|maintain|write) authorized=true ;; | ||
| esac | ||
| else | ||
| echo "::warning::Permission API call failed for $COMMENT_USER_LOGIN: $(cat "$api_err")" | ||
| fi | ||
| rm -f "$api_err" | ||
| else | ||
| echo "::warning::Failed to create temp file for permission check of $COMMENT_USER_LOGIN" | ||
| fi | ||
| fi | ||
| if [[ "$authorized" != "true" ]]; then | ||
| echo "::notice::User $COMMENT_USER_LOGIN is not authorized to stop the fix agent (requires write access or PR authorship)" | ||
| exit 0 | ||
| fi | ||
| gh label create "fullsend-no-fix" --repo "$REPO" \ | ||
| --description "Skip bot-triggered fix agent runs" --color "FBCA04" \ | ||
| 2>/dev/null || true | ||
| gh pr edit "$PR_NUMBER" --repo "$REPO" \ | ||
| --add-label "fullsend-no-fix" | ||
| gh pr comment "$PR_NUMBER" --repo "$REPO" \ | ||
| --body "Fix agent disabled for this PR. Remove the \`fullsend-no-fix\` label or use \`/fs-fix\` to re-engage." | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,59 @@ | ||
| # This file is managed by fullsend. Do not edit it directly. | ||
| # Upstream: https://github.com/fullsend-ai/fullsend/blob/main/internal/scaffold/fullsend-repo/.github/workflows/prioritize.yml | ||
| --- | ||
| # fullsend-stage: prioritize | ||
| name: Prioritize | ||
|
|
||
| permissions: | ||
| actions: write | ||
| contents: read | ||
| id-token: write | ||
| issues: write | ||
|
|
||
| on: | ||
| workflow_dispatch: | ||
| inputs: | ||
| event_type: | ||
| description: Event type that triggered prioritization | ||
| required: true | ||
| type: string | ||
| source_repo: | ||
| description: Repository the event came from (owner/repo) | ||
| required: true | ||
| type: string | ||
| event_payload: | ||
| description: JSON-encoded payload of the triggering event | ||
| required: true | ||
| type: string | ||
| project_number: | ||
| description: GitHub Projects V2 project number for RICE scoring | ||
| required: false | ||
| type: string | ||
|
|
||
| concurrency: | ||
| group: fullsend-prioritize-${{ inputs.source_repo }}-${{ fromJSON(inputs.event_payload).issue.number || fromJSON(inputs.event_payload).pull_request.number }} | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Prioritization runs for different Jira work items can cancel each other. Jira-sourced NormalizedEvent payloads carry The same expression exists in the pinned reusable workflow (
|
||
| cancel-in-progress: true | ||
|
|
||
| jobs: | ||
| prioritize: | ||
| uses: fullsend-ai/fullsend/.github/workflows/reusable-prioritize.yml@v0.56.1 | ||
| with: | ||
| event_type: ${{ inputs.event_type }} | ||
| source_repo: ${{ inputs.source_repo }} | ||
| event_payload: ${{ inputs.event_payload }} | ||
| mint_url: ${{ vars.FULLSEND_MINT_URL }} | ||
| gcp_region: ${{ vars.FULLSEND_GCP_REGION }} | ||
| project_number: ${{ inputs.project_number || vars.FULLSEND_PROJECT_NUMBER }} | ||
| runner_image: ubuntu-24.04 | ||
| secrets: | ||
| FULLSEND_GCP_WIF_PROVIDER: ${{ secrets.FULLSEND_GCP_WIF_PROVIDER }} | ||
| FULLSEND_GCP_PROJECT_ID: ${{ secrets.FULLSEND_GCP_PROJECT_ID }} | ||
| FULLSEND_OPENAI_API_KEY: ${{ secrets.FULLSEND_OPENAI_API_KEY }} | ||
| FULLSEND_INFERENCE_GATEWAY_API_KEY: ${{ secrets.FULLSEND_INFERENCE_GATEWAY_API_KEY }} | ||
| OTEL_EXPORTER_OTLP_TRACES_HEADERS: ${{ secrets.OTEL_EXPORTER_OTLP_TRACES_HEADERS }} | ||
| OTEL_EXPORTER_OTLP_HEADERS: ${{ secrets.OTEL_EXPORTER_OTLP_HEADERS }} | ||
| FULLSEND_JIRA_TOKEN: ${{ secrets.FULLSEND_JIRA_TOKEN }} | ||
| FULLSEND_JIRA_EMAIL: ${{ secrets.FULLSEND_JIRA_EMAIL }} | ||
| FULLSEND_JIRA_CLIENT_ID: ${{ secrets.FULLSEND_JIRA_CLIENT_ID }} | ||
| FULLSEND_JIRA_CLIENT_SECRET: ${{ secrets.FULLSEND_JIRA_CLIENT_SECRET }} | ||
| FULLSEND_GITHUB_RUNNER_SECRETS: ${{ secrets.FULLSEND_GITHUB_RUNNER_SECRETS }} | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -32,3 +32,6 @@ lerna-debug.log | |
| # For vim | ||
| *.swp | ||
| .yarn | ||
|
|
||
| # For Fullsend | ||
| .fullsend/.fullsend-cache | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Differs from chatbot fullsend PR, new block defining tracker.