CI for deploy to devtest - #574
Conversation
|
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 8934a5d. Configure here.

Summary
Closes #
Changes
How was this tested?
Checklist
pnpm build,pnpm test,pnpm typecheck,pnpm lint:ci, andpnpm format:checkpass locallypackages/trueforge-sdk,.github/fern/openapi/openapi.json,docs/openapi.json) — fork PRs omit SDK regen; maintainers regenerate after merge.env.exampleupdated if configuration or behavior changedNote
Low Risk
CI-only change that writes pinned SHAs to a separate devtest deployment repo using existing GitHub App secrets; no runtime application or auth logic in trueforge itself.
Overview
Adds a GitHub Actions workflow that keeps the devtest deployment repo in sync with
mainin this repository.On each push to
main(or manual run), the job checks outtruefoundry/trueforge-devtest-deployment, uses a GitHub App token, and updatestrueforge.truefoundry.yamlandtrueforge-controller.truefoundry.yamlsoimage.build_source.refandimage.build_source.branch_namepoint at the triggering commit and branch. It commits and pushes only when those pins change; concurrency is limited withdeploy-devtestand in-progress runs are cancelled.Reviewed by Cursor Bugbot for commit 88daabb. Bugbot is set up for automated code reviews on this repo. Configure here.