Maintain Effect GitHub Actions
When to Use
Review or update Effect GitHub Actions with a job-by-job trigger, revision, permission and artifact trust inventory.
Workflow
Identify affected workflows, composite actions and callers. For each job record trigger, actor, checked-out revision, token permissions, inputs and consumers of outputs and artifacts. Consult current official documentation for event and permission behavior. Use repository shared setup where applicable. Keep permissions minimal, pin actions to verified full SHAs, validate untrusted values as data, and align cancellation with job side effects. Run focused lint and report which checks need real GitHub execution.
Example
Review a workflow that consumes a build artifact and confirm the producing run, head and trust boundary before proposing a change.
Limitations
Requires the relevant Effect workspace and its versioned tools. Use local project policy and authorized fixtures. Results cover only the checked packages and environments.
Bundled resources
Use the bundled local references for the applicable branch of the workflow: privileged workflows. Run commands against the target Effect workspace.
Source
Adapted from the pinned skill tree. See the MIT license.
This snapshot of Effect v4 is vendored by Local Studio.