Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions .github/workflows/agents-guard.yml
Original file line number Diff line number Diff line change
Expand Up @@ -111,7 +111,7 @@ jobs:
github.event_name == 'pull_request_target' &&
steps.eligibility.outputs.should-run == 'true' &&
steps.api_client_base.outputs.available != 'true'
uses: "stranske/Workflows/.github/actions/setup-api-client@c2537cc959f2ce05926c4639d25b90678abc97bc" # v1
uses: "stranske/Workflows/.github/actions/setup-api-client@62ed0a86b5d57062ac3d04f4519e3998858e2d96" # v1

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major | πŸ—οΈ Heavy lift

Route this agents-guard.yml SHA bump through stranske/Workflows instead of patching the consumer workflow directly.

Line 114 and Line 183 both modify a local agents-*.yml file in the consumer repo; that creates upstream/downstream drift for future syncs. Apply this update in stranske/Workflows and sync it into consumers.

As per coding guidelines, "**/.github/workflows/agents-*.yml: agents-*.yml workflow files should be fixed in stranske/Workflows, not locally in the consumer repo."

Also applies to: 183-183

πŸ€– Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/agents-guard.yml at line 114, The SHA bump for the
setup-api-client action on line 114 (and the similar change on line 183) should
not be applied directly to the agents-guard.yml file in this consumer
repository. Instead, revert these changes from the local agents-guard.yml file
and apply the SHA bump update in the stranske/Workflows repository where the
agents-guard.yml template is maintained as the source of truth, then sync the
updated workflow back into this consumer repository to avoid upstream/downstream
drift.

Sources: Coding guidelines, Linked repositories

with:
secrets: ${{ toJSON(secrets) }}
github_token: ${{ github.token }}
Expand Down Expand Up @@ -180,7 +180,7 @@ jobs:
steps.eligibility.outputs.should-run == 'true' &&
github.event_name == 'pull_request' &&
steps.api_client_head.outputs.available != 'true'
uses: "stranske/Workflows/.github/actions/setup-api-client@c2537cc959f2ce05926c4639d25b90678abc97bc" # v1
uses: "stranske/Workflows/.github/actions/setup-api-client@62ed0a86b5d57062ac3d04f4519e3998858e2d96" # v1
with:
secrets: ${{ toJSON(secrets) }}
github_token: ${{ github.token }}
Expand Down
Loading