Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: do not run commitlint GitHub Action on dependabot PRs #3684

Merged
merged 2 commits into from
Feb 21, 2023

Conversation

nixpanic
Copy link
Member

Currently commitlint is only skipped for PR at the time dependabot creates them. Once Mergify rebases them, commitlint is started anyway. This causes failed CI runs, which then need to be ignored. It is cleaner to not run commitlint on any PR that dependabot owns.


Show available bot commands

These commands are normally not required, but in case of issues, leave any of
the following bot commands in an otherwise empty comment in this PR:

  • /retest ci/centos/<job-name>: retest the <job-name> after unrelated
    failure (please report the failure too!)
  • /retest all: run this in case the CentOS CI failed to start/report any test
    progress or results

@nixpanic nixpanic added component/testing Additional test cases or CI work ci/skip/e2e skip running e2e CI jobs ci/skip/multi-arch-build skip building on multiple architectures labels Feb 21, 2023
@nixpanic nixpanic requested a review from a team February 21, 2023 08:26
@nixpanic nixpanic requested a review from a team February 21, 2023 09:29
@nixpanic
Copy link
Member Author

/test all

Currently commitlint is only skipped for PR at the time dependabot
creates them. Once Mergify rebases them, commitlint is started anyway.
This causes failed CI runs, which then need to be ignored. It is cleaner
to not run commitlint on any PR that dependabot owns.

Signed-off-by: Niels de Vos <ndevos@redhat.com>
There is no need to run the `test-retest-action` GitHub Workflow if
there are no changes under the `actions/retest` directory.

Signed-off-by: Niels de Vos <ndevos@redhat.com>
@mergify mergify bot added the ok-to-test Label to trigger E2E tests label Feb 21, 2023
@nixpanic
Copy link
Member Author

/test all

@mergify mergify bot merged commit c84b4a1 into ceph:devel Feb 21, 2023
@nixpanic
Copy link
Member Author

Now testing in #3678 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci/skip/e2e skip running e2e CI jobs ci/skip/multi-arch-build skip building on multiple architectures component/testing Additional test cases or CI work ok-to-test Label to trigger E2E tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants