ci: skip most CI checks if title contains citest skip [citest_skip]

[richm]

When we submit a PR for a CI update or docs, we do not want to start CI checking
for ansible-lint, qemu, etc. When we are doing CI updates to 30 or more
roles, this fires off a lot of unnecessary tests, which sometimes causes the
linux-system-roles org in github to be throttled.

When submitting a PR that can skip ci, use "[citest_skip]" in the PR title.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Conditionally disables most CI workflow jobs when a pull request title contains the marker "[citest_skip]" to avoid running heavy checks on CI/docs-only changes.

File-Level Changes

Change	Details	Files
Gate all primary CI jobs on a PR title not containing the "[citest_skip]" marker.	Added a GitHub Actions job-level if condition using contains(github.event.pull_request.title, '[citest_skip]') to skip execution when the marker is present Applied this condition consistently across linting, testing, security analysis, spelling, markdown, shellcheck, QEMU integration, and README conversion workflows	.github/workflows/ansible-lint.yml .github/workflows/ansible-managed-var-comment.yml .github/workflows/ansible-test.yml .github/workflows/codeql.yml .github/workflows/codespell.yml .github/workflows/markdownlint.yml .github/workflows/python-unit-test.yml .github/workflows/qemu-kvm-integration-tests.yml .github/workflows/shellcheck.yml .github/workflows/test_converting_readme.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 - I've left some high level feedback:

• Several workflows (e.g., codeql with a scheduled cron trigger and any that run on push) reference github.event.pull_request.title, which will be undefined for non-PR events; consider guarding the condition with github.event_name == 'pull_request' or github.event.pull_request && ... so non-PR runs don’t fail or get unintentionally skipped.
• Since the same if: "!contains(github.event.pull_request.title, '[citest_skip]')" condition is duplicated across many jobs, consider applying the condition at the workflow level (or via a reusable workflow) to avoid repetition and reduce the risk of future jobs missing the skip logic.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Several workflows (e.g., codeql with a scheduled `cron` trigger and any that run on `push`) reference `github.event.pull_request.title`, which will be undefined for non-PR events; consider guarding the condition with `github.event_name == 'pull_request'` or `github.event.pull_request && ...` so non-PR runs don’t fail or get unintentionally skipped.
- Since the same `if: "!contains(github.event.pull_request.title, '[citest_skip]')"` condition is duplicated across many jobs, consider applying the condition at the workflow level (or via a reusable workflow) to avoid repetition and reduce the risk of future jobs missing the skip logic.

---

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