ci: re-stamp FuzeSDLC canonical workflow stack (bootstrap) - #206
Draft
fuze-agent[bot] wants to merge 1 commit into
Draft
ci: re-stamp FuzeSDLC canonical workflow stack (bootstrap)#206fuze-agent[bot] wants to merge 1 commit into
fuze-agent[bot] wants to merge 1 commit into
Conversation
Manual one-time re-stamp: this repo's stamped workflows predate the fuze:managed marker convention, so governance-sync (detect-only until now) could never reconcile .github/workflows/** on its own. Bootstraps the reconcile-capable governance-sync.yml, the claude-ci-autofix.yml -> fuze-ci-autofix.yml rename, the fuze-push-identity composite action, the governance-nightly fixes (bypassPermissions + deliverable verification + raised max-turns), and the rest of the current canonical STACK. The fleet-wide baselineRef=v1 alias is 86 commits behind FuzeSDLC main (last cut at v1.9.0), so this pins baselineRef to the exact FuzeSDLC main commit used to render these files (03fe67a36648431acf85f25c1a2a29f814b0699d) rather than either the stale v1 alias or the disallowed main branch. Recommend FuzeSDLC cut a new v1.x.0 release and re-point v1, after which this repo can move back to baselineRef: v1. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session-Id: fe3aa738-cb24-4315-a29b-29834ddea892
Contributor
|
Matched paths:
Consider updating `.claude/agents/fuzeagent-expert.md` to reflect any architectural changes. See governance/agent-ownership.md for the expert update workflow. |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| # ubuntu-latest puts one job back on a GitHub-hosted machine -- and on a | ||
| # private repo, never runs it at all. | ||
| runner: ubuntu-latest | ||
| secrets: inherit No newline at end of file |
| # ubuntu-latest puts one job back on a GitHub-hosted machine -- and on a | ||
| # private repo, never runs it at all. | ||
| runner: ubuntu-latest | ||
| secrets: inherit No newline at end of file |
| - name: Mint fuze-agent App installation token | ||
| id: app | ||
| if: inputs.app-id != '' && inputs.private-key != '' | ||
| uses: actions/create-github-app-token@v1 |
| - name: Mint fuze-agent App token | ||
| id: app_token | ||
| continue-on-error: true | ||
| uses: actions/create-github-app-token@v1 |
| - name: Mint fuze-agent App token | ||
| id: app_token | ||
| continue-on-error: true | ||
| uses: actions/create-github-app-token@v1 |
| # safe direction for a security gate is to run and go red, never to quietly not run. | ||
| - name: Upload SARIF (skipped on private repos — code scanning unavailable) | ||
| if: always() && !github.event.repository.private | ||
| uses: github/codeql-action/upload-sarif@v3 |
| # long note on the same step in gate-sast above for why this is not continue-on-error. | ||
| - name: Upload SARIF (skipped on private repos — code scanning unavailable) | ||
| if: always() && !github.event.repository.private | ||
| uses: github/codeql-action/upload-sarif@v3 |
| # long note on the same step in gate-sast above for why this is not continue-on-error. | ||
| - name: Upload SARIF (skipped on private repos — code scanning unavailable) | ||
| if: always() && !github.event.repository.private | ||
| uses: github/codeql-action/upload-sarif@v3 |
| - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1 | ||
| - uses: actions/setup-python@a26af69be951a213d495a4c3e4e4022e16d87065 # v5 | ||
| with: { python-version: '3.12' } | ||
| - uses: actions/setup-node@v7 |
| - name: Mint fuze-agent App token | ||
| id: app_token | ||
| continue-on-error: true | ||
| uses: actions/create-github-app-token@v1 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Manual one-time re-stamp: this repo's stamped workflows predate the
fuze:managed marker convention, so governance-sync (detect-only until now)
could never reconcile .github/workflows/** on its own. Bootstraps the
reconcile-capable governance-sync.yml, the claude-ci-autofix.yml ->
fuze-ci-autofix.yml rename, the fuze-push-identity composite action, the
governance-nightly fixes (bypassPermissions + deliverable verification +
raised max-turns), and the rest of the current canonical STACK.
The fleet-wide baselineRef=v1 alias is 86 commits behind FuzeSDLC main
(last cut at v1.9.0), so this pins baselineRef to the exact FuzeSDLC main
commit used to render these files (03fe67a36648431acf85f25c1a2a29f814b0699d)
rather than either the stale v1 alias or the disallowed main branch.
Recommend FuzeSDLC cut a new v1.x.0 release and re-point v1, after which
this repo can move back to baselineRef: v1.
Co-Authored-By: Claude Opus 5 noreply@anthropic.com
Claude-Session-Id: fe3aa738-cb24-4315-a29b-29834ddea892