You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit e045958
Browse filesBrowse the repository at this point in the historyBrowse files
feat: resolve secrets/vars expressions at dispatch and show full detection state
Expression resolution: workflows written GitHub-style never received their
secrets - `KEY: ${{ secrets.API_KEY }}` shipped to the container as that
literal string. dispatch now substitutes `${{ secrets.NAME }}` and
`${{ vars.NAME }}` blocks (dot or bracket form, single-ref expressions
only) in plan env values and step run strings: known secrets resolve to
their value, unknown secrets and vars to "" (GitHub's unset semantics).
Substitution lives in dispatch memory only - stored plans keep literals,
reruns pick up rotated values, masks register after substitution, and
secret plaintexts remain unconditional log masks.
Detection visibility: the requirements endpoints now return EVERY detected
(name, repository) pair with configured state and the covering secret's /
matching environment's id, not just missing names. The cards become
repo-grouped "Detected in workflows" lists - configured entries link to
their detail pages for editing, missing ones keep one-click Add/Create,
and reserved-prefix secret refs (DOCKER_*, GITHUB_*) are shown with an
explanation instead of being silently hidden (shared secretNameRules
module). The workflow detail Metadata tab gains Variables referenced and
Environments sections plus a re-sync hint when the stored parse predates
detection, and the pipeline Environment tab shows the job's deployment
environment binding.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
0 commit comments