Skip to content

chore(ci): adopt reusable workflow templates#573

Merged
KooshaPari merged 2 commits into
mainfrom
ci/adopt-reusables
Jun 1, 2026
Merged

chore(ci): adopt reusable workflow templates#573
KooshaPari merged 2 commits into
mainfrom
ci/adopt-reusables

Conversation

@KooshaPari

@KooshaPari KooshaPari commented Jun 1, 2026

Copy link
Copy Markdown
Owner

User description

Use shared reusable trufflehog/cargo-deny workflows from phenotype-tooling.


Note

Low Risk
CI-only refactor with no application code changes; behavior now depends on external reusable workflows pinned to @main.

Overview
cargo-deny and Trufflehog workflows no longer run their steps inline. Each job now delegates to shared reusable workflows in KooshaPari/phenotype-tooling on main, matching the pattern already used for SBOM refresh.

For cargo-deny, the local checkout, Rust toolchain, and EmbarkStudios/cargo-deny-action steps (including ./codex-rs defaults) are removed, and the workflow_dispatch trigger is dropped so only PR and push-to-main runs remain.

For Trufflehog, the checkout, setup, and trufflehog github --only-verified run are replaced by the reusable workflow; trigger coverage stays PR plus push to main.

Reviewed by Cursor Bugbot for commit a0e2291. Bugbot is set up for automated code reviews on this repo. Configure here.


CodeAnt-AI Description

Move secret and dependency scans to shared CI workflows

What Changed

  • Trufflehog and cargo-deny now run through shared reusable workflows instead of being defined inline in this repo
  • cargo-deny no longer has a manual trigger; it runs on pull requests and pushes to main
  • Trufflehog still runs on pull requests and pushes to main

Impact

✅ Consistent security checks across repositories
✅ Fewer CI maintenance updates
✅ Less chance of missed secret and dependency scan runs

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

@gemini-code-assist

Copy link
Copy Markdown

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

@codeant-ai

codeant-ai Bot commented Jun 1, 2026

Copy link
Copy Markdown

CodeAnt AI is reviewing your PR.


Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

@codeant-ai codeant-ai Bot added the size:XS This PR changes 0-9 lines, ignoring generated files label Jun 1, 2026
@codeant-ai

codeant-ai Bot commented Jun 1, 2026

Copy link
Copy Markdown

CodeAnt AI finished reviewing your PR.

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

Bugbot Autofix prepared a fix for the issue found in the latest run.

  • ✅ Fixed: Missing codex-rs cargo-deny target
    • Restored cargo-deny to run against codex-rs/Cargo.toml via manifest-path so the production Rust workspace and deny.toml are enforced instead of the minimal root package.

Create PR

Or push these changes by commenting:

@cursor push df0972a0c9
Preview (df0972a0c9)
diff --git a/.github/workflows/cargo-deny.yml b/.github/workflows/cargo-deny.yml
--- a/.github/workflows/cargo-deny.yml
+++ b/.github/workflows/cargo-deny.yml
@@ -6,4 +6,18 @@
       - main
 jobs:
   cargo-deny:
-    uses: KooshaPari/phenotype-tooling/.github/workflows/reusable/cargo-deny.yml@main
+    runs-on: ubuntu-24.04
+    steps:
+      - name: Checkout
+        uses: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5 # v4.2.2
+
+      - name: Install Rust toolchain
+        uses: dtolnay/rust-toolchain@3c5f7ea28cd621ae0bf5283f0e981fb97b8a7af9
+        with:
+          toolchain: stable
+
+      - name: Run cargo-deny
+        uses: EmbarkStudios/cargo-deny-action@91bf2b620e09e18d6eb78b92e7861937469acedb # v6
+        with:
+          rust-version: stable
+          manifest-path: codex-rs/Cargo.toml

You can send follow-ups to the cloud agent here.

Reviewed by Cursor Bugbot for commit a0e2291. Configure here.

Comment thread .github/workflows/cargo-deny.yml
@KooshaPari KooshaPari merged commit 9f65eb5 into main Jun 1, 2026
10 checks passed
@KooshaPari KooshaPari deleted the ci/adopt-reusables branch June 1, 2026 05:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:XS This PR changes 0-9 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant