Skip to content

ci: do not run ci tests by default, require citest comment or label [citest_skip] - #338

Merged
richm merged 1 commit into
mainfrom
no-ci-without-comment
Sep 2, 2026
Merged

ci: do not run ci tests by default, require citest comment or label [citest_skip]#338
richm merged 1 commit into
mainfrom
no-ci-without-comment

Conversation

@richm

@richm richm commented Sep 2, 2026

Copy link
Copy Markdown
Collaborator

github action ci jobs are a precious resource - we only have 20 jobs - when multiple
PRs are submitted we may have to wait hours to get results. We need to be explicit
about where and when to run ci jobs.

With this change, when a PR is created or updated, CI tests will not run automatically.
A role maintainer (OWNER, MEMBER, COLLABORATOR, or systemroller) must either comment
on the PR or add a label:

  • [citest_all] comment or citest_all label - run all CI tests, including checks
    and Testing Farm integration tests
  • [citest_$test] comment or citest_$test label - run only that test - for
    example, [citest_ansible-lint] or the citest_ansible-lint label
  • For Testing Farm, [citest_tft] / citest_tft runs those tests. [citest] /
    citest is still accepted for Testing Farm for backward compatibility.

Comments work on issue_comment; labels take effect when the PR is opened, when new
commits are pushed, or when the label is added. These labels are managed by
system roles .github automation.
See linux-system-roles/.github#186

If you use the gh command to interact with github, you can use
gh pr comment $PRNUM -b '[citest_all]'
or
gh pr edit $PRNUM --add-label citest_all

Signed-off-by: Rich Megginson [email protected]

@richm richm self-assigned this Sep 2, 2026
…citest_skip]

github action ci jobs are a precious resource - we only have 20 jobs - when multiple
PRs are submitted we may have to wait hours to get results.  We need to be explicit
about where and when to run ci jobs.

With this change, when a PR is created or updated, CI tests will not run automatically.
A role maintainer (OWNER, MEMBER, COLLABORATOR, or systemroller) must either comment
on the PR or add a label:

* `[citest_all]` comment or `citest_all` label - run all CI tests, including checks
  and Testing Farm integration tests
* `[citest_$test]` comment or `citest_$test` label - run only that test - for
  example, `[citest_ansible-lint]` or the `citest_ansible-lint` label
* For Testing Farm, `[citest_tft]` / `citest_tft` runs those tests.  `[citest]` /
  `citest` is still accepted for Testing Farm for backward compatibility.

Comments work on issue_comment; labels take effect when the PR is opened, when new
commits are pushed, or when the label is added.  These labels are managed by
system roles .github automation.
See linux-system-roles/.github#186

If you use the `gh` command to interact with github, you can use
`gh pr comment $PRNUM -b '[citest_all]'`
or
`gh pr edit $PRNUM --add-label citest_all`

Signed-off-by: Rich Megginson <[email protected]>
@coderabbitai

coderabbitai Bot commented Sep 2, 2026

Copy link
Copy Markdown

Important

Review skipped

Ignore keyword(s) in the title.

⛔ Ignored keywords (1)
  • [citest_skip]

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Team

Run ID: 64512948-5e1b-4a8b-9f71-112fbb92b2b1

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@richm
richm merged commit 3a8b7b2 into main Sep 2, 2026
15 checks passed
@richm
richm deleted the no-ci-without-comment branch September 2, 2026 20:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant