Repository navigation
fix(ci): reuse the shared deny workflow - #250
Merged
Merged
Conversation
Keep runner protection and cargo-deny installation in tempoxyz/ci while preserving the caller configuration. Co-authored-by: Derek Cofausper <256792747+decofe@users.noreply.github.com>
Reuse the existing shared deny workflow without changing its action or adding runner and timeout inputs. Co-authored-by: Derek Cofausper <256792747+decofe@users.noreply.github.com>
decofe
enabled auto-merge (squash)
September 22, 2026 21:21
DaniPopes
approved these changes
Sep 22, 2026
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
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.
Replace the inline cargo-deny setup with a pinned call to
tempoxyz/ci/.github/workflows/deny.yml, keeping the job ID, permissions, toolchain, deny flags, and trigger conditions. This reuses the existing shared workflow and its vendored cargo-deny action without changing that workflow.Prompted by: @DaniPopes