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.
feat: implement issue #253 — Compliance: non-stub-agent-shield.yml #268
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uh oh!
There was an error while loading. Please reload this page.
feat: implement issue #253 — Compliance: non-stub-agent-shield.yml #268
Changes from all commits
58e8c997032dacc49d4a1e59d46fFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This overrides the reusable workflow’s pinned
ecc-agentshielddefault withlatest, so the required AgentShield check can change behavior or start failing when a new npm release is published, without any change in this repo. In CI contexts where this check gates merges, keep this input on a concrete version so scan policy and failures remain reproducible.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With the v1 reusable workflow,
org-standards-refis passed directly togrep -qiE "$ORG_REF" AGENTS.mdin the “Validate cross-references” step. The current repository’sAGENTS.mdreferencespetry-projects/.github/blob/main/..., so this new value (petry-projects/.github/main) does not match and the AgentShield job will fail on every push/PR even though the required org-standards link is present.Useful? React with 👍 / 👎.
Uh oh!
There was an error while loading. Please reload this page.