Checkout repo before running path-filter job

[Praveen2112]

Description

The path-filter CI job when run on master requires the repo to be checked out.

Additional context and related issues

Release notes

( ) This is not user-visible or is docs only, and no release notes are required.
( ) Release notes are required. Please propose a release note for me.
( ) Release notes are required, with the following suggested text:

## Section
* Fix some things. ({issue}`issuenumber`)

Summary by Sourcery

CI:

• Insert actions/checkout@v5 as the first step in the path-filter job with a conditional ref expression for repository_dispatch events

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

The CI path-filter job has been updated to explicitly checkout the repository before running the filter action, using a conditional ref expression to support both pull_request and repository_dispatch events.

Sequence diagram for conditional repository checkout in path-filter job

sequenceDiagram
  participant CI as "CI Runner"
  participant GH as "GitHub Actions"
  participant Repo as "Repository"
  CI->>GH: Start path-filter job
  GH->>Repo: Checkout code (actions/checkout@v5)
  alt repository_dispatch event
    GH->>Repo: Checkout ref "refs/pull/{number}/head"
  else other events
    GH->>Repo: Checkout default branch
  end
  GH->>GH: Run dorny/paths-filter action
  GH->>CI: Output filter results

Loading

File-Level Changes

Change	Details	Files
Add repo checkout step preceding the path-filter action	Inserted actions/checkout@v5 at the start of the path-filter job steps Added a conditional ref expression to resolve pull request SHA on repository_dispatch events	.github/workflows/ci.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 there - I've reviewed your changes and they look great!

---

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.}

[findepi]

This won't work correctly.
It will detect no changes, and then jobs won't run.

see

• Fix ci workflow on master #27094

[Copilot]

Pull Request Overview

This PR adds a repository checkout step to the path-filter CI job to ensure the repository is available before the path-filter action executes. This is particularly necessary when the workflow runs on the master branch.

Key Changes:

• Added actions/checkout@v5 step before the path-filter action with conditional ref handling for repository_dispatch events

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

[nitpick] The multi-line conditional expression for the ref parameter is complex and difficult to parse. Consider extracting this logic into a separate step that sets an environment variable or output, making the checkout step's configuration clearer and easier to maintain.