ci: bump gha checkout from v5 to v6

[richm]

bump gha checkout from v5 to v6

Signed-off-by: Rich Megginson rmeggins@redhat.com

Summary by Sourcery

Build:

• Bump actions/checkout from v5 to v6 in all GitHub Actions workflow files.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates all GitHub Actions workflows to use actions/checkout v6 instead of v5 to keep CI dependencies current and consistent.

File-Level Changes

Change	Details	Files
Bump actions/checkout from v5 to v6 across all CI workflows.	Updated build_docs workflow checkout steps to use actions/checkout@v6 for main, docs, and sparse-checkout operations. Updated tft workflow to use actions/checkout@v6 for both initial repository checkout and PR-specific checkout. Updated ansible-related workflows (ansible-lint, ansible-managed-var-comment, ansible-test) to use actions/checkout@v6 for repository checkout. Updated additional CI workflows (changelog_to_tag, codeql, codespell, markdownlint, pr-title-lint, python-unit-test, qemu-kvm-integration-tests, test_converting_readme, weekly_ci, woke) to reference actions/checkout@v6 for their checkout steps.	.github/workflows/build_docs.yml .github/workflows/tft.yml .github/workflows/ansible-lint.yml .github/workflows/ansible-managed-var-comment.yml .github/workflows/ansible-test.yml .github/workflows/changelog_to_tag.yml .github/workflows/codeql.yml .github/workflows/codespell.yml .github/workflows/markdownlint.yml .github/workflows/pr-title-lint.yml .github/workflows/python-unit-test.yml .github/workflows/qemu-kvm-integration-tests.yml .github/workflows/test_converting_readme.yml .github/workflows/weekly_ci.yml .github/workflows/woke.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 - here's some feedback:

• Consider pinning actions/checkout to a specific commit SHA (with an inline comment noting v6) instead of @v6 to reduce the risk of unexpected changes from future releases.
• In workflows where you perform multiple actions/checkout steps for the same repository/branch within a single job, consider whether some of these can be consolidated or replaced with git commands to reduce redundant checkouts and speed up CI.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider pinning `actions/checkout` to a specific commit SHA (with an inline comment noting v6) instead of `@v6` to reduce the risk of unexpected changes from future releases.
- In workflows where you perform multiple `actions/checkout` steps for the same repository/branch within a single job, consider whether some of these can be consolidated or replaced with `git` commands to reduce redundant checkouts and speed up CI.

---

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