mirror of
https://github.com/ceph/ceph-csi.git
synced 2025-06-13 10:33:35 +00:00
ci: add github action to trigger E2E
based on the discussion on the slack channel. we are adding a github action to trigger the CI jobs when a ok-to-test label is added on the PR. This action is based on below github action https://github.com/peter-evans/create-or-update-comment Sample Demo avaiable at https://github.com/Madhu-1/ \label-commentor-action-testing/pull/4 Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
This commit is contained in:
committed by
mergify[bot]
parent
2cc1a276fc
commit
659567cfdc
@ -252,6 +252,7 @@ A few labels interact with automation around the pull requests:
|
||||
* DNM: DO NOT MERGE (Mergify will not merge this PR)
|
||||
* ci/skip/e2e: skip running e2e CI jobs
|
||||
* ci/skip/multi-arch-build: skip building container images for different architectures
|
||||
* ok-to-test: PR is ready for e2e testing.
|
||||
|
||||
**Review Process:**
|
||||
Once your PR has been submitted for review the following criteria will
|
||||
@ -268,6 +269,9 @@ need to be met before it will be merged:
|
||||
community feedback.
|
||||
* The 24 working hours counts hours occurring Mon-Fri in the local timezone
|
||||
of the submitter.
|
||||
* ceph-csi-maintainers/ceph-csi-contributors can add `ok-to-test` label to the
|
||||
pull request when they think it is ready for e2e testing. This is done to avoid
|
||||
load on the CI.
|
||||
* Each PR must be fully updated to devel and tests must have passed
|
||||
* If the PR is having trivial changes or the reviewer is confident enough that
|
||||
PR doesn't need a second review, the reviewer can set `ready-to-merge` label
|
||||
|
Reference in New Issue
Block a user