ci: Use org-wide Warden workflow#111
Merged
Merged
Conversation
Rely on the org-wide Warden workflow and keep repository-specific skill configuration in warden.toml. Set the Warden runtime to pi so configured built-in skills resolve through Warden instead of depending on a stale repo-local action pin. Co-Authored-By: OpenAI Codex <noreply@openai.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
This removes the repo-local Warden workflow and relies on the org-wide Warden workflow instead. The repository still owns its Warden behavior through
warden.toml.\n\nThe config now opts into thepiruntime so configured built-in Warden skills resolve as built-ins instead of depending on a stale repo-local action pin.\n\nValidation:\n-pnpm check\n-pnpx @sentry/warden@latest add --list