Skip to content

feat(#7814): gate GitLab fix fork/cross-project MRs on a protected-branch check - #7946

Merged
ggallen merged 2 commits into
mainfrom
agent/7814-gitlab-fork-mr-push-back
Oct 2, 2026
Merged

ggallen merged 2 commits into
mainfrom
agent/7814-gitlab-fork-mr-push-back

Conversation

@fullsend-ai-coder

Copy link
Copy Markdown
Contributor

Summary

Extends #7816's GitLab fix-agent pre-script checkout to let fork and
cross-project MRs actually run, and adds the pre-push safety check
that checkout-mr-source.sh's own comments called out as this PR's
precondition.

  • run-agent-job.sh's job-level fork gate now only denies the code
    stage (which opens a new MR against the target project and has no
    validated source revision to fall back on). fix is no longer
    gated on IS_FORK at all — it relies entirely on
    checkout-mr-source.sh's own resolve/fetch/checkout validation
    (fullsend resolve-mr-source, unchanged by this PR), which already
    works for fork and cross-project sources since feat(#7814): check out GitLab fork and cross-project MR sources #7816.
  • Added fullsend check-protected-branch (internal/cli/checkprotectedbranch.go),
    a thin wrapper over the existing forge.Client.IsProtectedBranch/
    GetProtectedBranch GitLab implementation. checkout-mr-source.sh
    calls it against the resolved SOURCE_PROJECT_PATH/SOURCE_BRANCH
    (never the target project) before fetching, and fails the job closed
    if that branch is protected — by an exact-name rule or a matching
    wildcard rule — or if protection status can't be determined.

Scope boundary (please read before reviewing)

The actual git push for the fix stage — along with the post-script's
summary comments, labels, and status/failure handling — is performed
by the runner-side post-script shipped in fullsend-ai/agents, not by
any file in this repository. There is no post-fix.sh/post-code.sh
in this checkout to modify, and fullsend run's internal
sandbox-extraction lifecycle (internal/cli/run.go) means a GitLab
scaffold script has no way to reach the agent's committed tree after
fullsend run returns — the sandbox is already deleted by then, and
the extracted copy only exists as an env var (REPO_DIR) passed to
fullsend run's own internal post-script subprocess, which this repo
does not configure.

This PR implements the half of the post-script slice that is owned
by this repository: lifting the job-level gate and adding the pre-push
protected-branch check, so that by the time the external post-script
runs, SOURCE_PROJECT_PATH/SOURCE_BRANCH (already exported by #7816
"for post-scripts") describe a project/branch that is both the genuine
MR source and confirmed safe to push to. Coordinating the
fullsend-ai/agents post-script to push to SOURCE_PROJECT_PATH/
SOURCE_BRANCH instead of assuming same-project is necessarily a
separate change in that repository.

Changes

  • internal/scaffold/fullsend-repo-gitlab/.gitlab/ci/scripts/run-agent-job.sh:
    fork gate now covers only code; expanded comments on the gate and
    on PUSH_TOKEN to describe the fix stage's push destination.
  • internal/scaffold/fullsend-repo-gitlab/.gitlab/ci/scripts/checkout-mr-source.sh:
    new pre-push protected-branch check before the fetch; updated header
    comment.
  • internal/cli/checkprotectedbranch.go (+ root.go registration):
    new fullsend check-protected-branch command.
  • docs/agents/fix.md: documents the completed GitLab pre/post-script
    ownership split for fork and cross-project MRs.
  • docs/ADRs/0067-gitlab-cron-polling-event-dispatch.md: minor
    annotation (not a rewrite) noting the fix stage's fork handling
    changed.

Testing

  • go test -race ./internal/cli/ -run 'TestCheckProtectedBranch'
  • go test -race ./internal/scaffold/ -run 'TestCheckoutMRSource|TestGitLabAgentTemplate|TestRunAgentJobScript'
  • go build ./..., go vet ./... clean
  • gofmt -l clean on all changed files
  • shellcheck -x -e SC1091,SC2001,SC2016 (pinned to the repo hook's
    v0.10.0.1 rev) clean on both changed scripts
  • hack/lint-adr-status, hack/lint-adr-numbers pass
  • Patch coverage on internal/cli/checkprotectedbranch.go: 100% /
    95.2% by function
  • pre-commit itself could not fetch its remote hook repos in this
    sandbox (TLS/network restriction); ran the equivalent checks above
    directly instead. scan-secrets --staged (gitleaks-equivalent)
    passed.
  • Two pre-existing test failures on main before this change
    (TestStartFetchService_*, TestPostScriptEnv_NoSchemaAppended*)
    are unrelated sandbox network-permission / ambient-env artifacts of
    this coding session, not a regression from this diff.

Related to #7814

Post-script verification

  • Branch is not main/master (agent/7814-gitlab-fork-mr-push-back)
  • Secret scan passed (gitleaks — 4f2746c618d53a06ffa4bd7ef915328981f351a5..HEAD)
  • PR body secret scan passed (gitleaks — no-git)

…anch check

Extends #7816's pre-script checkout to let fix-stage GitLab dispatches
proceed on fork and cross-project merge requests, and adds the
pre-push safety check that was its stated precondition.

run-agent-job.sh's job-level fork gate previously denied both "code"
and "fix" whenever IS_FORK was true. "code" opens a new MR against the
target project and has no analogous validated source revision, so it
keeps the deny-by-default behavior unconditionally. "fix" no longer
checks IS_FORK at all: checkout-mr-source.sh (#7816) already resolves,
fetches, and verifies the exact MR source project/branch/SHA through
fullsend resolve-mr-source, independent of the attacker-influenced
IS_FORK pipeline variable, so that validation is what makes it safe to
run on a fork or cross-project MR.

Before this change, that validated checkout had no accompanying
pre-push safety gate: a resolved source branch could be protected
(exact-name or wildcard rule) and the job would still fetch it and run
the agent. Added a new fullsend check-protected-branch CLI command
(internal/cli/checkprotectedbranch.go) that wraps the existing
forge.Client.IsProtectedBranch/GetProtectedBranch GitLab implementation
(internal/forge/gitlab/ci.go, unchanged) and fails closed -- on a
protected branch or an inconclusive API result alike.
checkout-mr-source.sh calls it against the resolved
SOURCE_PROJECT_PATH/SOURCE_BRANCH (never FULLSEND_PINNED_PROJECT_PATH)
before fetching, so a fix commit can never be attempted against a
protected branch regardless of which project it lives in.

Scope boundary worth flagging for review: the actual git push for the
fix stage (and the post-script's summary comments, labels, and status
handling) is performed by the runner-side post-script that ships in
fullsend-ai/agents, not by any file in this repository -- there is no
post-fix.sh/post-code.sh here to modify, and fullsend run's internal
sandbox-extraction lifecycle (internal/cli/run.go) means a GitLab
scaffold script cannot reach the agent's committed tree after fullsend
run returns (the sandbox is already deleted by then). This PR's
responsibility is therefore the half owned by this repo: lifting the
job-level gate and adding the pre-push protected-branch check, so that
by the time the external post-script runs, SOURCE_PROJECT_PATH and
SOURCE_BRANCH (already exported by #7816 "for post-scripts") describe
a project/branch that is both the genuine MR source and confirmed safe
to push to.

Updated docs/agents/fix.md's GitLab section and run-agent-job.sh's and
checkout-mr-source.sh's comments to describe the completed pre-script
ownership and the fork gate split between "code" (still denied) and
"fix" (validated instead of denied). Added a minor annotation to ADR
0067 noting the fix stage's fork-handling has changed, without
rewriting its accepted Context/Decision text.

Tests: internal/cli/checkprotectedbranch_test.go (new; unit + cobra
command-level cases: not protected, exact-rule protected,
wildcard-rule protected, invalid project path, API error, missing
flags -- 100%/95.2% function coverage); internal/scaffold/
checkout_mr_source_test.go (extended the shared fullsend stub to
answer check-protected-branch, added same-project and fork
protected-branch fail-closed cases); internal/scaffold/
scaffold_gitlab_test.go (replaced the loose code/fix fork-check
assertion with one that inspects the actual guarding if, added a test
proving "fix" is no longer gated and that checkout-mr-source.sh
invokes the new check); internal/scaffold/gitlab_job_scripts_test.go
(added check-protected-branch to one inline fullsend stub that
exercises the fix-stage happy path end to end).

Verification: go build/vet ./... clean; go test -race on internal/cli
and internal/scaffold (all pass except TestStartFetchService_* and
TestPostScriptEnv_NoSchemaAppended*, which fail identically on main
before this change -- sandbox network-permission and ambient-env
artifacts of this harness session, unrelated to this diff); gofmt
clean; shellcheck (pinned to the hook's v0.10.0.1 rev) on both changed
scripts; hack/lint-adr-status and hack/lint-adr-numbers pass on the
touched ADR; patch coverage on internal/cli/checkprotectedbranch.go is
100%/95.2% by function. pre-commit itself could not fetch its remote
hook repos in this sandbox (TLS/network restriction), so the above
direct-equivalent checks were run in its place; the gitleaks-equivalent
scan-secrets passed on staged content.

Related to #7814
@fullsend-ai-coder
fullsend-ai-coder Bot requested a review from a team October 1, 2026 21:38
@fullsend-ai-coder fullsend-ai-coder Bot added the ready-for-review Triggers review agent dispatch label Oct 1, 2026
@fullsend-ai-review

fullsend-ai-review Bot commented Oct 1, 2026 •

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 9:39 PM UTC · Completed 9:57 PM UTC

Commit: 0aa836d · View workflow run →

Runtime: pi · Model: openai/gpt-6.1-sol → gpt-6.1-sol · Effort: high · Cost: $4.57

@github-actions

github-actions Bot commented Oct 1, 2026 •

Copy link
Copy Markdown

Site preview

Preview: https://6e92c5ec-site.fullsend-ai.workers.dev

Commit: 82d4fe561694cb40738d452daf3620f7b03bd211

@codecov

codecov Bot commented Oct 1, 2026

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 96.29630% with 2 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
internal/cli/checkprotectedbranch.go 96.22% 1 Missing and 1 partial ⚠️

📢 Thoughts on this report? Let us know!

@fullsend-ai-review fullsend-ai-review Bot added the risk/moderate PR risk: moderate label Oct 1, 2026
@fullsend-ai-review

fullsend-ai-review Bot commented Oct 1, 2026 •

Copy link
Copy Markdown

Risk Assessment: moderate (2/5)

Details

Moderate risk: bot-authored change with matching issue scope and no protected path or dependency modifications, balanced against elevated regression history and tight change coupling across GitLab CI scaffold components.

Previous run

Risk Assessment: moderate (2/5)

Details

Moderate risk: bot-authored change with matching issue scope and no protected path or dependency modifications, balanced against elevated regression history and tight change coupling across GitLab CI scaffold components.

@fullsend-ai-review

fullsend-ai-review Bot commented Oct 1, 2026 •

Copy link
Copy Markdown

Looks good to me


Labels: The PR adds a Go CLI command and tests alongside the already-labeled GitLab CI changes.

Previous run

Review

Findings

High

  • [api-contract] internal/scaffold/fullsend-repo-gitlab/.gitlab/ci/scripts/run-agent-job.sh:377 — Removing fix from the fork gate enables a checkout whose existing post-script redirects publication to the target project. The inspected fullsend-ai/agents/scripts/post-fix.sh constructs GitLab origin from REPO_FULL_NAME, while internal/cli/run.go derives that value from --status-repo and this scaffold supplies FULLSEND_PINNED_PROJECT_PATH. Exported SOURCE_PROJECT_PATH is not consumed for the push remote. A same-named target branch can therefore receive the fix, or the missing-remote-ref path can attempt to create that branch in the target project. See also the rbac-violation finding at this location.
    Remediation: Retain the fork/cross-project fix gate until a compatible post-script is shipped and selected. Separate source push identity from target MR/comment identity and integration-test same-project, fork, and cross-project publication destinations.

  • [rbac-violation] internal/scaffold/fullsend-repo-gitlab/.gitlab/ci/scripts/run-agent-job.sh:377 — The newly enabled fork path does not enforce the credential-bearing write boundary. Source project, branch, checkout SHA, and pre-run protection are validated, but the inspected publication consumer uses target REPO_FULL_NAME for its authenticated push remote instead of SOURCE_PROJECT_PATH. Checkout validation therefore does not restrict writes to the validated source repository. See also the api-contract finding at this location.
    Remediation: Keep fork/cross-project fix jobs denied until a compatible consumer is selected through a pinned revision or explicit capability requirement. Require publication-time source identity validation and tests demonstrating that fork branch names cannot direct writes into the target repository.

Medium

  • [edge-case] internal/scaffold/fullsend-repo-gitlab/.gitlab/ci/scripts/checkout-mr-source.sh:460 — Protection is checked before fetching and running the agent, not before publication. A branch can become protected during that interval, and the inspected post-script pushes without repeating the lookup. GitLab rejection does not enforce the stated policy of refusing every protected source branch because a protection rule can permit the selected identity to push.
    Remediation: Retain the early check and repeat source identity validation and the exact/wildcard protection lookup immediately before publication. Fail closed on lookup errors and test protection added after checkout; do not describe a recheck as an atomic guarantee.

  • [incorrect-doc] docs/agents/fix.md:67 — The new text states that the runner-side post-script pushes to the validated source project and never the target project. The inspected existing consumer instead constructs its GitLab push remote from target REPO_FULL_NAME. This PR neither implements nor requires the claimed publication behavior.
    Remediation: Document the implemented checkout/protection slice and pending publication dependency accurately. Keep fork execution gated until compatible source-targeted publication is available, and align the script comments with that state.

  • [test-inadequate] internal/cli/checkprotectedbranch_test.go:27 — The custom ServeMux handlers do not track or assert invocation, contrary to the explicit httptest convention in docs/contributing/go-code.md. An unmatched exact-name route also returns the expected 404, so the unprotected case can pass without exercising the intended exact-name handler when the wildcard listing succeeds.
    Remediation: Track and assert invocation of both expected endpoints in the API-backed tests.

  • [api-contract] internal/scaffold/fullsend-repo-gitlab/.gitlab/ci/scripts/run-agent-job.sh:607 — Cross-project publication reuses FULLSEND_JOB_TOKEN as PUSH_TOKEN without establishing source-project write access. The installation documented in docs/contributing/gitlab-role-credentials.md provisions a Coder project access token for the installed project. Correcting the consumer's destination alone therefore does not establish that publication to an unrelated source project can succeed.
    Remediation: Define and test the supported source-project authorization arrangement, or explicitly document unsupported sources and their intentional failure handling. Do not silently broaden the target credential.

Low

  • [api-shape] internal/cli/checkprotectedbranch_test.go:28 — The exact-name test handler calls WriteHeader before setting Content-Type, so the subsequent header change is not transmitted to the client. This reduces fixture fidelity; it is not an established production failure.
    Remediation: Set Content-Type before calling WriteHeader.

  • [missing-doc] docs/guides/dev/cli-internals.md:186 — The manually maintained CLI command tree omits the newly registered check-protected-branch helper and its --project, --branch, --gitlab-url, and --token flags.
    Remediation: Add the helper and its flags to the command tree.

  • [missing-doc] docs/contributing/documentation.md:125 — The Minor commands inventory omits check-protected-branch alongside the existing resolve-mr-source helper.
    Remediation: Add check-protected-branch to the inventory.


Labels: PR changes GitLab CI job scripts and fork-fix gating.


Next steps:

  • /fs-fix — agent addresses review findings automatically
  • /fs-fix <your instruction> — agent fixes with your specific guidance
  • Push commits directly — review re-runs automatically on push
  • /fs-fix-stop — disable automatic fix runs for this PR

fullsend-ai-review[bot]

This comment was marked as outdated.

@fullsend-ai-review fullsend-ai-review Bot added the component/ci CI pipelines and checks label Oct 1, 2026
@fullsend-ai-coder

fullsend-ai-coder Bot commented Oct 1, 2026 •

Copy link
Copy Markdown
Contributor Author

🤖 Finished Fix · ✅ Success · Started 10:00 PM UTC · Completed 10:16 PM UTC

Commit: 0aa836d · View workflow run →

Runtime: claude · Model: sonnet → claude-sonnet-5 · Effort: high · Cost: $2.74

…ource-aware

Review found that this PR's fork-gate removal for the "fix" stage was
unsafe: checkout-mr-source.sh validates and fetches the resolved MR
source, but the runner-side post-script that actually pushes the fix
commit still targets this job's own project/branch rather than the
validated source — so a fork or cross-project dispatch could end up
pushing into (or trying to create a branch in) the target project
under its credentials. Re-gate "fix" on IS_FORK alongside "code" (same
as before this PR) while keeping the new check-protected-branch
tooling and checkout-time validation in place for when a
source-targeted publish path ships. Corrected docs/comments that
claimed the post-script already pushes to the validated source project
(docs/agents/fix.md, run-agent-job.sh, checkout-mr-source.sh, the ADR).

Also:
- internal/cli/checkprotectedbranch_test.go: track and assert
  invocation of both fake-GitLab-API endpoints so the "not protected"
  tests actually exercise the intended handlers, and set Content-Type
  before WriteHeader in the exact-name handler.
- docs/guides/dev/cli-internals.md, docs/contributing/documentation.md:
  document the new check-protected-branch command.

Addresses #7946
@fullsend-ai-coder

Copy link
Copy Markdown
Contributor Author

🔧 Fix agent — iteration 1 (bot-triggered)

The two HIGH findings (api-contract, rbac-violation) both point to the same root cause: this PR lifted the job-level IS_FORK gate for the 'fix' stage on the assumption that the runner-side post-script pushes the fix commit back to the validated MR source project, but the inspected post-script (in a different repository) actually constructs its push remote from the target project. Verified this against the code and re-gated 'fix' on IS_FORK alongside 'code', restoring the pre-PR deny-by-default behavior for fork/cross-project fix dispatches, while keeping the new check-protected-branch CLI and checkout-time validation as groundwork for a future PR once publish-side support ships. Corrected every doc/comment that claimed the post-script already targets the source project (docs/agents/fix.md, the ADR, and both scaffold scripts) to match. Also fixed the two independent, non-security test findings in checkprotectedbranch_test.go (handler invocation tracking, Content-Type/WriteHeader ordering) and added the two missing-doc entries for the new check-protected-branch command. Recorded a disagreement on the edge-case (TOCTOU) finding: the recheck-before-publish it asks for would need to live in the external post-script, which is out of this PR's/repo's scope; re-gating the fork path closed removes the only route that currently reaches the affected check for an untrusted source. Project CI was inspected and is fully green (no pr-related failures).

Fixed (8):

  1. [HIGH api-contract] Removing the fork gate for the fix stage enables a checkout whose existing post-script redirects publication to the target project (run-agent-job.sh:377) (internal/scaffold/fullsend-repo-gitlab/.gitlab/ci/scripts/run-agent-job.sh): Verified: the runner-side post-script that pushes the fix commit constructs its GitLab push remote from the job's own REPO_FULL_NAME/target project, not the resolved SOURCE_PROJECT_PATH, and that publication consumer lives outside this repo so it can't be fixed in this PR. Re-gated the 'fix' stage on IS_FORK alongside 'code' (restoring pre-PR behavior) so fork/cross-project fix dispatches are denied again, while keeping the new checkout-time validation and check-protected-branch tooling in place for when a source-targeted publish path ships.
  2. [HIGH rbac-violation] The newly enabled fork path does not enforce the credential-bearing write boundary; publication uses target REPO_FULL_NAME instead of SOURCE_PROJECT_PATH (run-agent-job.sh:377) (internal/scaffold/fullsend-repo-gitlab/.gitlab/ci/scripts/run-agent-job.sh): Same root cause and same fix as the api-contract finding above: fork/cross-project fix jobs are denied again at the job-level gate, so checkout validation is no longer the sole write-boundary enforcement for an unreachable path.
  3. [MEDIUM incorrect-doc] docs/agents/fix.md:67 states the post-script pushes only to the validated source project and never the target project, which the inspected consumer does not implement (docs/agents/fix.md): Rewrote the GitLab fork/cross-project MR section to accurately describe the implemented checkout/protected-branch slice and the pending publish-side dependency, and to state that both code and fix remain denied by the IS_FORK gate until that dependency ships.
  4. [MEDIUM test-inadequate] internal/cli/checkprotectedbranch_test.go:27 — custom ServeMux handlers do not track or assert invocation (internal/cli/checkprotectedbranch_test.go): Added invocation counters to protectedBranchAPIServer and asserted both the exact-name and wildcard-listing endpoints were actually hit in the tests that exercise them.
  5. [MEDIUM api-contract] run-agent-job.sh:607 — cross-project publication reuses FULLSEND_JOB_TOKEN as PUSH_TOKEN without establishing source-project write access (internal/scaffold/fullsend-repo-gitlab/.gitlab/ci/scripts/run-agent-job.sh): Reverted the PUSH_TOKEN comment's claim that this token is used to push to the validated source project; with fork/cross-project fix dispatches denied again (see HIGH findings), this credential is only ever used for same-project pushes, same as before this PR.
  6. [LOW api-shape] internal/cli/checkprotectedbranch_test.go:28 — WriteHeader called before Content-Type is set in the exact-name test handler (internal/cli/checkprotectedbranch_test.go): Reordered the handler to set Content-Type before calling WriteHeader when returning the 200 OK fixture body.
  7. [LOW missing-doc] docs/guides/dev/cli-internals.md:186 — command tree omits check-protected-branch and its flags (docs/guides/dev/cli-internals.md): Added the check-protected-branch entry with its --project, --branch, --gitlab-url, and --token flags to the command tree.
  8. [LOW missing-doc] docs/contributing/documentation.md:125 — Minor commands inventory omits check-protected-branch (docs/contributing/documentation.md): Added check-protected-branch to the minor commands inventory.

Disagreed (1):

  1. [MEDIUM edge-case] Protected-branch check runs before fetch/run, not immediately before publication; a branch could become protected in between (checkout-mr-source.sh:460): The actual push happens in the runner-side post-script, which lives in a different repository (fullsend-ai/agents) not touched by this PR, so a repeat protected-branch check immediately before publication cannot be implemented from this repo. Re-gating fork/cross-project fix dispatches closed (see the two HIGH findings) removes the only path that currently reaches this checkout logic for an untrusted source, substantially narrowing the exposure; the TOCTOU window for same-project fix dispatches is a pre-existing, lower-severity characteristic of this check that is out of this PR's reach. Updated the surrounding comments so they no longer imply the fork/cross-project path is already safe to run.

Tests: passed

CI inspections (13):

  1. CI / test (passing, success)
  2. CI / test-sandbox-darwin (passing, success)
  3. CI / web (passing, success)
  4. CI / commit-lint (passing, success)
  5. E2E Tests / behaviour (passing, success)
  6. E2E Tests / e2e (passing, success)
  7. E2E Tests / gate (passing, success)
  8. Functional Tests / functional-tests (passing, success)
  9. Functional Tests / gate (passing, success)
  10. Build Site / build (passing, success)
  11. Vouch Check / vouch-gate (passing, success)
  12. codecov/patch (passing, success)
  13. DCO (passing, success)
Decision points
  • Chose to re-gate the fix stage on IS_FORK (restoring pre-PR behavior) rather than trying to make the post-script source-aware (alternatives: Leave the fork gate lifted and attempt to fix the push-destination bug, Revert the fork-gate change but drop the new check-protected-branch tooling entirely; rationale: The publication consumer that determines push destination lives in a different repository (fullsend-ai/agents) not touched by this PR, so it cannot be made source-aware from here. Both HIGH findings explicitly recommend retaining the gate until a compatible post-script is shipped and selected. Keeping the new checkout-time validation and check-protected-branch CLI (rather than dropping them) preserves the safety-relevant groundwork for the follow-up PR that will actually lift the gate.)

Next steps:

  • /fs-review — request a re-review of the changes
  • /fs-fix <your instruction> — run another fix pass with specific guidance
  • Push commits directly — review re-runs automatically on push
    Updated by fullsend fix agent

@fullsend-ai-review

fullsend-ai-review Bot commented Oct 1, 2026 •

Copy link
Copy Markdown

🤖 Finished Review · ✅ Success · Started 10:18 PM UTC · Completed 10:29 PM UTC

Commit: 82d4fe5 · View workflow run →

Runtime: pi · Model: openai/gpt-6.1-sol → gpt-6.1-sol · Effort: high · Cost: $2.38

@fullsend-ai-review fullsend-ai-review Bot added ready-for-merge All reviewers approved — ready to merge go Pull requests that update go code labels Oct 1, 2026
@ggallen
ggallen enabled auto-merge October 1, 2026 22:50
@ggallen
ggallen added this pull request to the merge queue Oct 1, 2026
Merged via the queue into main with commit 19329e3 Oct 2, 2026
70 of 72 checks passed

This branch was successfully deployed

1 active and 1 inactive deployments
dev — 82d4fe56 Deployed Oct 1, 2026 by fullsend-ai-coder[bot] via behaviour #14921
site-preview — 82d4fe56 Deployed Oct 1, 2026 by github-actions[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

component/ci CI pipelines and checks go Pull requests that update go code ready-for-merge All reviewers approved — ready to merge ready-for-review Triggers review agent dispatch risk/moderate PR risk: moderate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant