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

Adds a conditional to multiple GitHub Actions workflows so that most CI jobs are skipped when the pull request title contains the marker "[citest_skip]".

Flow diagram for CI job execution decision based on PR title

flowchart TD
  A["PR_opened_or_updated"] --> B["Read_pull_request_title"]
  B --> C{Title_contains_citest_skip_marker}
  C -->|yes| D["Evaluate_if_expression_false"]
  D --> E["Skip_CI_job_execution"]
  C -->|no| F["Evaluate_if_expression_true"]
  F --> G["Run_CI_job_steps"]

Loading

File-Level Changes

Change	Details	Files
Gate CI jobs on a PR title flag to allow skipping most checks.	Add an if condition to each affected GitHub Actions job to check that the pull request title does not contain the substring "[citest_skip]" Apply this conditional gating consistently across linting, spelling, markdown, integration test, README conversion, and inclusive-language workflows	.github/workflows/ansible-lint.yml .github/workflows/ansible-managed-var-comment.yml .github/workflows/ansible-test.yml .github/workflows/codespell.yml .github/workflows/markdownlint.yml .github/workflows/qemu-kvm-integration-tests.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:

• Consider also skipping these jobs when the PR title is updated after the workflow has already started (e.g., via a pull_request_target or pull_request edited trigger plus if at the workflow level), otherwise adding [citest_skip] later will not prevent already-running checks.
• Relying on a magic string in the title is easy to miss; you might want to support a PR label (e.g. ci-skip) and check contains(join(github.event.pull_request.labels.*.name, ' '), 'ci-skip') instead or in addition, so skipping can be managed more reliably from the UI or automation.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider also skipping these jobs when the PR title is updated after the workflow has already started (e.g., via a `pull_request_target` or `pull_request` `edited` trigger plus `if` at the workflow level), otherwise adding `[citest_skip]` later will not prevent already-running checks.
- Relying on a magic string in the title is easy to miss; you might want to support a PR label (e.g. `ci-skip`) and check `contains(join(github.event.pull_request.labels.*.name, ' '), 'ci-skip')` instead or in addition, so skipping can be managed more reliably from the UI or automation.

---

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