test: validate exhort-integration-tests TC-4813

[a-oren]

Summary

• Points integration workflow to a-oren/exhort-integration-tests@TC-4813 to validate syft image analysis scenarios before merging

Related

• exhort-integration-tests PR: feat(syft): add Dockerfile/Containerfile image analysis scenarios for hardened recommendations trustification/exhort-integration-tests#38

Test plan

• Integration tests pass with the updated workflow reference

🤖 Generated with Claude Code

Summary by Sourcery

CI:

• Point integration workflow to use the exhort-integration-tests reusable workflow from the TC-4813 branch in the a-oren fork.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Update integration GitHub Actions workflow to run the integration tests from a feature branch in a forked exhort-integration-tests repository, in order to validate syft image analysis scenarios before merging.

File-Level Changes

Change	Details	Files
Point integration workflow to use a fork/feature-branch version of exhort-integration-tests instead of main in the upstream repo.	Change the reusable workflow reference in the integration job to use the a-oren/exhort-integration-tests repository. Pin the reusable workflow to the TC-4813 branch instead of main. Keep all workflow inputs and job conditions unchanged to isolate the impact to the workflow source reference.	.github/workflows/integration.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• Referencing a personal fork and branch (a-oren/exhort-integration-tests@TC-4813) in a shared workflow can be fragile; consider pinning to a specific commit SHA or a tag and adding a follow-up to revert back to trustification/...@main once validation is complete.
• If this temporary workflow change is only for validation, you may want to guard it with a condition or a clear TODO comment in the YAML to avoid accidentally running against the forked workflow long term.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Referencing a personal fork and branch (`a-oren/exhort-integration-tests@TC-4813`) in a shared workflow can be fragile; consider pinning to a specific commit SHA or a tag and adding a follow-up to revert back to `trustification/...@main` once validation is complete.
- If this temporary workflow change is only for validation, you may want to guard it with a condition or a clear TODO comment in the YAML to avoid accidentally running against the forked workflow long term.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.75%. Comparing base (ab5949f) to head (fc739a8).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #567   +/-   ##
=======================================
  Coverage   90.75%   90.75%           
=======================================
  Files          36       36           
  Lines        7766     7766           
  Branches     1353     1353           
=======================================
  Hits         7048     7048           
  Misses        718      718           

Flag	Coverage Δ
unit-tests	90.75% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.