mirrors/ceph-csi
1
0
Fork 0
mirror of https://github.com/ceph/ceph-csi.git synced 2025-06-14 18:53:35 +00:00
Code Issues Packages Projects Releases Wiki Activity
Files
437d90c84d25c8c1e0dba7e9b246d3572eb5b3aa
ceph-csi/.mergify.yml

481 lines
18 KiB
YAML
Raw Normal View History

Fix yaml lint error in mergify Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
2019-03-22 10:57:56 +05:30
---
ci: move from merge action to queue action as mentioned in the below blog the support for strict mode and merge action will be done soon in mergify. This brings the change requested for the same. Ref# https://blog.mergify.com/strict-mode-deprecation/ Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
2022-01-10 15:33:25 +05:30
queue_rules:
- name: default
ci: update mergify config to replace,remove deprecated attributes update mergify config to remove, replace the deprecated attributes. Signed-off-by: Nikhil-Ladha <nikhilladha1999@gmail.com>
2024-08-21 10:21:47 +05:30
merge_conditions:
ci: move from merge action to queue action as mentioned in the below blog the support for strict mode and merge action will be done soon in mergify. This brings the change requested for the same. Ref# https://blog.mergify.com/strict-mode-deprecation/ Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
2022-01-10 15:33:25 +05:30
# Conditions to get out of the queue (= merged)
- or:
- and:
ci: use regex comparing `~=` for `release-v*` branch checking It seems that `base=release-v*` does not match the `release-v3.10` branch for some reason. Maybe a Mergify update requires stricter checking of strings, and only allows the `~=` operator for regular expressions now? Regular expressions like `base~=^(devel)|(release-.+)$` seem to match for `release-3.10`, so let's use that notation everywhere. Signed-off-by: Niels de Vos <ndevos@ibm.com>
2023-12-01 10:14:41 +01:00
- base~=^(release-.+)$
ci: move from merge action to queue action as mentioned in the below blog the support for strict mode and merge action will be done soon in mergify. This brings the change requested for the same. Ref# https://blog.mergify.com/strict-mode-deprecation/ Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
2022-01-10 15:33:25 +05:30
- "status-success=codespell"
- "status-success=multi-arch-build"
- "status-success=go-test"
- "status-success=golangci-lint"
- "status-success=mod-check"
- "status-success=lint-extras"
ci: add test for uncommitted changes in deploy directory added test for uncommitted changes in deploy directory under go-test GH action. Also, created a new make target named `make check-deploy-committed` that can be used to verify the uncommitted changes. Signed-off-by: Nikhil-Ladha <nikhilladha1999@gmail.com>
2024-08-13 12:29:40 +05:30
- "status-success=uncommitted-code-check"
ci: update rule for ci/skip/e2e updates mergify rules to handle ci/skip/e2e label Signed-off-by: ShravaniVangur <shravanivangur@gmail.com>
2025-03-11 14:39:25 +05:30
- or:
- label=ci/skip/e2e
- and:
- "status-success=ci/centos/k8s-e2e-external-storage/1.29"
- "status-success=ci/centos/k8s-e2e-external-storage/1.30"
- "status-success=ci/centos/k8s-e2e-external-storage/1.31"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.29"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.30"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.31"
- "status-success=ci/centos/mini-e2e/k8s-1.29"
- "status-success=ci/centos/mini-e2e/k8s-1.30"
- "status-success=ci/centos/mini-e2e/k8s-1.31"
- "status-success=ci/centos/upgrade-tests-cephfs"
- "status-success=ci/centos/upgrade-tests-rbd"
ci: update mergify rules for release branches Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2024-01-03 23:25:40 +05:30
- and:
ci: update mergify rules updating mergify rules to drop 3.11 and add 3.13 support. Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
2024-12-03 08:13:02 +01:00
- base=release-v3.12
ci: update mergify rules for release branches Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2024-01-03 23:25:40 +05:30
- "status-success=codespell"
- "status-success=multi-arch-build"
- "status-success=go-test"
- "status-success=golangci-lint"
- "status-success=mod-check"
- "status-success=lint-extras"
ci: update rule for ci/skip/e2e updates mergify rules to handle ci/skip/e2e label Signed-off-by: ShravaniVangur <shravanivangur@gmail.com>
2025-03-11 14:39:25 +05:30
- or:
- label=ci/skip/e2e
- and:
- "status-success=ci/centos/k8s-e2e-external-storage/1.29"
- "status-success=ci/centos/k8s-e2e-external-storage/1.30"
- "status-success=ci/centos/k8s-e2e-external-storage/1.31"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.29"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.30"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.31"
- "status-success=ci/centos/mini-e2e/k8s-1.29"
- "status-success=ci/centos/mini-e2e/k8s-1.30"
- "status-success=ci/centos/mini-e2e/k8s-1.31"
- "status-success=ci/centos/upgrade-tests-cephfs"
- "status-success=ci/centos/upgrade-tests-rbd"
ci: skip kube 1.25 check for devel branch Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2023-08-25 17:44:49 +05:30
- and:
- base=devel
- "status-success=codespell"
- "status-success=multi-arch-build"
- "status-success=go-test"
- "status-success=golangci-lint"
- "status-success=mod-check"
- "status-success=lint-extras"
ci: add test for uncommitted changes in deploy directory added test for uncommitted changes in deploy directory under go-test GH action. Also, created a new make target named `make check-deploy-committed` that can be used to verify the uncommitted changes. Signed-off-by: Nikhil-Ladha <nikhilladha1999@gmail.com>
2024-08-13 12:29:40 +05:30
- "status-success=uncommitted-code-check"
ci: update rule for ci/skip/e2e updates mergify rules to handle ci/skip/e2e label Signed-off-by: ShravaniVangur <shravanivangur@gmail.com>
2025-03-11 14:39:25 +05:30
- or:
- label=ci/skip/e2e
- and:
- "status-success=ci/centos/k8s-e2e-external-storage/1.30"
- "status-success=ci/centos/k8s-e2e-external-storage/1.31"
- "status-success=ci/centos/k8s-e2e-external-storage/1.32"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.30"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.31"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.32"
- "status-success=ci/centos/mini-e2e/k8s-1.30"
- "status-success=ci/centos/mini-e2e/k8s-1.31"
- "status-success=ci/centos/mini-e2e/k8s-1.32"
- "status-success=ci/centos/upgrade-tests-cephfs"
- "status-success=ci/centos/upgrade-tests-rbd"
ci: move from merge action to queue action as mentioned in the below blog the support for strict mode and merge action will be done soon in mergify. This brings the change requested for the same. Ref# https://blog.mergify.com/strict-mode-deprecation/ Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
2022-01-10 15:33:25 +05:30
- and:
- base=ci/centos
- "status-success=ci/centos/job-validation"
- "status-success=ci/centos/jjb-validate"
ci: update mergify config to replace,remove deprecated attributes update mergify config to remove, replace the deprecated attributes. Signed-off-by: Nikhil-Ladha <nikhilladha1999@gmail.com>
2024-08-21 10:21:47 +05:30
merge_method: rebase
update_method: rebase
build: use ceph-csi-bot account for mergify actions Mergify does now support a `defaults:` section. It can be used to configure the `bot_account:` in a single location. CC: @ceph-csi-bot Signed-off-by: Niels de Vos <ndevos@redhat.com>
2021-03-01 08:46:47 +01:00
add mergify as a merge engine From now on, each PR will be merged automatically if: * there is no DNM label on the PR AND * the PR has at least one approuval AND * the travis CI successfully passed Closes: https://github.com/ceph/ceph-csi/issues/154 Signed-off-by: Sébastien Han <seb@redhat.com>
2019-01-31 18:03:31 +01:00
pull_request_rules:
ci: add `ok-to-test` label to all PRs in the merge queue It seems that some PRs still get rebased by Mergify, whereas others get tested for the **merge queue** by creating a new temporary PR. In both cases the `ok-to-test` label should get set automatically. Fixes: c4d372e (ci: automatically add `ok-to-test` to PRs created by Mergify) Signed-off-by: Niels de Vos <ndevos@ibm.com>
2023-05-11 13:34:10 +02:00
- name: start CI jobs for PRs in the merge queue
ci: automatically remove `ok-to-test` and set it when queuing a PR The `ok-to-test` label currently needs to be removed and re-added when a PR is rebased for re-queuing. It should be possible to automate this, by removing the `ok-to-test` label when a PR gets queued. It can automatically be added again when the PR has embarked the merge train. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2022-11-09 14:29:20 +01:00
conditions:
- base~=^(devel)|(release-.+)$
ci: do not add the `ok-to-test` label if there is a conflict When there is a conflict in merging a PR, the `ok-to-test` label should not be added automatically. This prevents a loop in triggering CI jobs for PRs that might not even build. Signed-off-by: Niels de Vos <ndevos@ibm.com>
2024-04-11 17:24:35 +02:00
- label!=conflicts
ci: update rule for ci/skip/e2e updates mergify rules to handle ci/skip/e2e label Signed-off-by: ShravaniVangur <shravanivangur@gmail.com>
2025-03-11 14:39:25 +05:30
- label!=ci/skip/e2e
ci: only add `ok-to-test` if there are no pending CentOS jobs After the `ok-to-test` label was added, the commenter will remove the label again. There is no need for Mergify to re-add the label while CI jobs are still running. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2023-02-20 16:59:35 +01:00
- not:
check-pending~=^ci/centos
ci: do not add `ok-to-test` if CentOS jobs were successful Mergify does not add the `ok-to-test` label immediately anymore. But once the CentOS CI jobs have finished, the label still gets added. With the additional check, this should not be the case anymore. Signed-off-by: Niels de Vos <ndevos@ibm.com>
2023-02-22 12:56:59 +01:00
- not:
status-success~=^ci/centos
ci: add `ok-to-test` label to all PRs in the merge queue It seems that some PRs still get rebased by Mergify, whereas others get tested for the **merge queue** by creating a new temporary PR. In both cases the `ok-to-test` label should get set automatically. Fixes: c4d372e (ci: automatically add `ok-to-test` to PRs created by Mergify) Signed-off-by: Niels de Vos <ndevos@ibm.com>
2023-05-11 13:34:10 +02:00
- or:
- "check-pending=Queue: Embarked in merge train"
ci: fix author=mergify[bot] Author of mergifyio created pr is mergify[bot]. It needs the suffix `[bot]` for the condition to be evaluated to true. Signed-off-by: Rakshith R <rar@redhat.com>
2023-05-15 11:01:08 +05:30
- author=mergify[bot]
ci: automatically remove `ok-to-test` and set it when queuing a PR The `ok-to-test` label currently needs to be removed and re-added when a PR is rebased for re-queuing. It should be possible to automate this, by removing the `ok-to-test` label when a PR gets queued. It can automatically be added again when the PR has embarked the merge train. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2022-11-09 14:29:20 +01:00
actions:
label:
add:
- ok-to-test
mergify: Remove approved review when a PR changes When people have reviewed a PR, and the contributor updates it, the reviews are staying valid. This is unfortunate as the PR might need new corrections. Ideally a positive review (Approved) needs to be given again. And there needs to be a confirmation that a negative review (Changes requested) has been addressed. Closes: #505 Signed-off-by: Niels de Vos <ndevos@redhat.com>
2019-09-02 13:45:21 +02:00
- name: remove outdated approvals
conditions:
ci: drop quotes for Mergify regex matching The matching with regexes on the `base=` configuration in Mergify does not seem to work as intended. Possibly this is due the addtional quotes around the regex. Fixes: 8d7c66363 (ci: apply standard Mergify rules for release branches too) Signed-off-by: Niels de Vos <ndevos@redhat.com>
2021-05-04 10:30:32 +02:00
- base~=^(devel)|(release-.+)$
mergify: Remove approved review when a PR changes When people have reviewed a PR, and the contributor updates it, the reviews are staying valid. This is unfortunate as the PR might need new corrections. Ideally a positive review (Approved) needs to be given again. And there needs to be a confirmation that a negative review (Changes requested) has been addressed. Closes: #505 Signed-off-by: Niels de Vos <ndevos@redhat.com>
2019-09-02 13:45:21 +02:00
actions:
dismiss_reviews:
approved: true
changes_requested: false
ci: automatically remove `ok-to-test` and set it when queuing a PR The `ok-to-test` label currently needs to be removed and re-added when a PR is rebased for re-queuing. It should be possible to automate this, by removing the `ok-to-test` label when a PR gets queued. It can automatically be added again when the PR has embarked the merge train. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2022-11-09 14:29:20 +01:00
ci: Add mergify rule for conflict Added mergify rules to post a message when there is conflict on the PR. ref: https://doc.mergify.io/examples.html#request-for-action Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
2020-05-14 16:15:01 +05:30
- name: ask to resolve conflict
conditions:
- conflict
ci: prevent mergify conflict message for dependabot PRs There is no use in having Mergify posting messages to Dependabot and asking for resolving of merge conflicts. Dependabot will try to do that automatically, and posts a message when some other action is needed. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2021-09-02 08:27:59 +02:00
- author!=dependabot[bot]
ci: Add mergify rule for conflict Added mergify rules to post a message when there is conflict on the PR. ref: https://doc.mergify.io/examples.html#request-for-action Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
2020-05-14 16:15:01 +05:30
actions:
comment:
ci: update mergify config to replace,remove deprecated attributes update mergify config to remove, replace the deprecated attributes. Signed-off-by: Nikhil-Ladha <nikhilladha1999@gmail.com>
2024-08-21 10:21:47 +05:30
# yamllint disable-line rule:truthy rule:line-length
message: "This pull request now has conflicts with the target branch. Could you please resolve conflicts and force push the corrected changes? 🙏"
ci: automatically remove `ok-to-test` and set it when queuing a PR The `ok-to-test` label currently needs to be removed and re-added when a PR is rebased for re-queuing. It should be possible to automate this, by removing the `ok-to-test` label when a PR gets queued. It can automatically be added again when the PR has embarked the merge train. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2022-11-09 14:29:20 +01:00
ci: skip commitlint for dependabot PRs Dependabot creates commit messages that commitlint fails to parse correctly. The messages contain simple references to which dependencies are updated, and do not need full validation like manual written messages do. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2021-08-30 17:08:19 +02:00
- name: update dependencies by dependabot (skip commitlint)
conditions:
ci: remove condition for dependabot dependabot will not create PR on the release branch and for that reason removing unused rule Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
2024-04-02 10:29:48 +02:00
- author=dependabot[bot]
- label!=DNM
- base=devel
- "#approved-reviews-by>=2"
- "#changes-requested-reviews-by=0"
- "approved-reviews-by=@ceph/ceph-csi-contributors"
- "approved-reviews-by=@ceph/ceph-csi-maintainers"
- "status-success=codespell"
- "status-success=multi-arch-build"
- "status-success=go-test"
- "status-success=golangci-lint"
- "status-success=mod-check"
- "status-success=lint-extras"
- "status-success=DCO"
ci: update rule for ci/skip/e2e updates mergify rules to handle ci/skip/e2e label Signed-off-by: ShravaniVangur <shravanivangur@gmail.com>
2025-03-11 14:39:25 +05:30
- or:
- label=ci/skip/e2e
- and:
- "status-success=ci/centos/k8s-e2e-external-storage/1.30"
- "status-success=ci/centos/k8s-e2e-external-storage/1.31"
- "status-success=ci/centos/k8s-e2e-external-storage/1.32"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.30"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.31"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.32"
- "status-success=ci/centos/mini-e2e/k8s-1.30"
- "status-success=ci/centos/mini-e2e/k8s-1.31"
- "status-success=ci/centos/mini-e2e/k8s-1.32"
- "status-success=ci/centos/upgrade-tests-cephfs"
- "status-success=ci/centos/upgrade-tests-rbd"
ci: skip commitlint for dependabot PRs Dependabot creates commit messages that commitlint fails to parse correctly. The messages contain simple references to which dependencies are updated, and do not need full validation like manual written messages do. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2021-08-30 17:08:19 +02:00
actions:
ci: move from merge action to queue action as mentioned in the below blog the support for strict mode and merge action will be done soon in mergify. This brings the change requested for the same. Ref# https://blog.mergify.com/strict-mode-deprecation/ Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
2022-01-10 15:33:25 +05:30
queue:
name: default
ci: skip commitlint for dependabot PRs Dependabot creates commit messages that commitlint fails to parse correctly. The messages contain simple references to which dependencies are updated, and do not need full validation like manual written messages do. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2021-08-30 17:08:19 +02:00
delete_head_branch: {}
ci: don't dismiss review if PR has not merged Pull requests are not going to be queued if at the same time the pull request review are dismiss Original-author: Mehdi ABAAKOUK <sileht@sileht.net> Signed-off-by: Niels de Vos <ndevos@redhat.com>
2022-01-11 19:41:51 +01:00
- name: dismiss review of merged pull request
conditions:
- base~=^(devel)|(release-.+)$
- merged
actions:
dismiss_reviews: {}
add mergify as a merge engine From now on, each PR will be merged automatically if: * there is no DNM label on the PR AND * the PR has at least one approuval AND * the travis CI successfully passed Closes: https://github.com/ceph/ceph-csi/issues/154 Signed-off-by: Sébastien Han <seb@redhat.com>
2019-01-31 18:03:31 +01:00
- name: automatic merge
conditions:
ci: skip kube 1.25 check for devel branch Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2023-08-25 17:44:49 +05:30
- or:
- and:
- label!=DNM
ci: use regex comparing `~=` for `release-v*` branch checking It seems that `base=release-v*` does not match the `release-v3.10` branch for some reason. Maybe a Mergify update requires stricter checking of strings, and only allows the `~=` operator for regular expressions now? Regular expressions like `base~=^(devel)|(release-.+)$` seem to match for `release-3.10`, so let's use that notation everywhere. Signed-off-by: Niels de Vos <ndevos@ibm.com>
2023-12-01 10:14:41 +01:00
- base~=^(release-.+)$
ci: skip kube 1.25 check for devel branch Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2023-08-25 17:44:49 +05:30
- "#approved-reviews-by>=2"
- "#changes-requested-reviews-by=0"
- "approved-reviews-by=@ceph/ceph-csi-contributors"
- "approved-reviews-by=@ceph/ceph-csi-maintainers"
ci: update Mergify config for automatic merging of backports to 3.10 The `queue_rules` were updated earlier, but the rule for moving a backport PR to the queue was not. By splitting the conditions for release-v3.9 and other (newer) releases, the PRs can be queued with their required Kubernetes version tests. Signed-off-by: Niels de Vos <ndevos@ibm.com>
2023-12-07 10:16:55 +01:00
- "status-success=DCO"
- "status-success=codespell"
- "status-success=commitlint"
- "status-success=go-test"
- "status-success=golangci-lint"
ci: update mergify rules for release branches Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2024-01-03 23:25:40 +05:30
- "status-success=lint-extras"
- "status-success=mod-check"
- "status-success=multi-arch-build"
ci: add test for uncommitted changes in deploy directory added test for uncommitted changes in deploy directory under go-test GH action. Also, created a new make target named `make check-deploy-committed` that can be used to verify the uncommitted changes. Signed-off-by: Nikhil-Ladha <nikhilladha1999@gmail.com>
2024-08-13 12:29:40 +05:30
- "status-success=uncommitted-code-check"
ci: update rule for ci/skip/e2e updates mergify rules to handle ci/skip/e2e label Signed-off-by: ShravaniVangur <shravanivangur@gmail.com>
2025-03-11 14:39:25 +05:30
- or:
- label=ci/skip/e2e
- and:
- "status-success=ci/centos/k8s-e2e-external-storage/1.29"
- "status-success=ci/centos/k8s-e2e-external-storage/1.30"
- "status-success=ci/centos/k8s-e2e-external-storage/1.31"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.29"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.30"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.31"
- "status-success=ci/centos/mini-e2e/k8s-1.29"
- "status-success=ci/centos/mini-e2e/k8s-1.30"
- "status-success=ci/centos/mini-e2e/k8s-1.31"
- "status-success=ci/centos/upgrade-tests-cephfs"
- "status-success=ci/centos/upgrade-tests-rbd"
ci: update Mergify config for automatic merging of backports to 3.10 The `queue_rules` were updated earlier, but the rule for moving a backport PR to the queue was not. By splitting the conditions for release-v3.9 and other (newer) releases, the PRs can be queued with their required Kubernetes version tests. Signed-off-by: Niels de Vos <ndevos@ibm.com>
2023-12-07 10:16:55 +01:00
- and:
- label!=DNM
ci: update mergify rules updating mergify rules to drop 3.11 and add 3.13 support. Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
2024-12-03 08:13:02 +01:00
- base=release-v3.12
ci: update Mergify config for automatic merging of backports to 3.10 The `queue_rules` were updated earlier, but the rule for moving a backport PR to the queue was not. By splitting the conditions for release-v3.9 and other (newer) releases, the PRs can be queued with their required Kubernetes version tests. Signed-off-by: Niels de Vos <ndevos@ibm.com>
2023-12-07 10:16:55 +01:00
- "#approved-reviews-by>=2"
- "#changes-requested-reviews-by=0"
- "approved-reviews-by=@ceph/ceph-csi-contributors"
- "approved-reviews-by=@ceph/ceph-csi-maintainers"
ci: skip kube 1.25 check for devel branch Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2023-08-25 17:44:49 +05:30
- "status-success=codespell"
- "status-success=multi-arch-build"
- "status-success=go-test"
- "status-success=golangci-lint"
- "status-success=commitlint"
- "status-success=mod-check"
- "status-success=lint-extras"
- "status-success=DCO"
ci: update rule for ci/skip/e2e updates mergify rules to handle ci/skip/e2e label Signed-off-by: ShravaniVangur <shravanivangur@gmail.com>
2025-03-11 14:39:25 +05:30
- or:
- label=ci/skip/e2e
- and:
- "status-success=ci/centos/k8s-e2e-external-storage/1.29"
- "status-success=ci/centos/k8s-e2e-external-storage/1.30"
- "status-success=ci/centos/k8s-e2e-external-storage/1.31"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.29"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.30"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.31"
- "status-success=ci/centos/mini-e2e/k8s-1.29"
- "status-success=ci/centos/mini-e2e/k8s-1.30"
- "status-success=ci/centos/mini-e2e/k8s-1.31"
- "status-success=ci/centos/upgrade-tests-cephfs"
- "status-success=ci/centos/upgrade-tests-rbd"
ci: do not require Kubernetes 1.26 tests for the devel branch Kubernetes 1.26 is End-Of-Life, the next version of Ceph-CSI will not support that anymore. Signed-off-by: Niels de Vos <ndevos@ibm.com>
2024-04-23 13:37:34 +02:00
- and:
- label!=DNM
- base=devel
- "#approved-reviews-by>=2"
- "#changes-requested-reviews-by=0"
- "approved-reviews-by=@ceph/ceph-csi-contributors"
- "approved-reviews-by=@ceph/ceph-csi-maintainers"
- "status-success=codespell"
- "status-success=multi-arch-build"
- "status-success=go-test"
- "status-success=golangci-lint"
- "status-success=commitlint"
- "status-success=mod-check"
- "status-success=lint-extras"
- "status-success=DCO"
ci: update rule for ci/skip/e2e updates mergify rules to handle ci/skip/e2e label Signed-off-by: ShravaniVangur <shravanivangur@gmail.com>
2025-03-11 14:39:25 +05:30
- or:
- label=ci/skip/e2e
- and:
- "status-success=ci/centos/k8s-e2e-external-storage/1.30"
- "status-success=ci/centos/k8s-e2e-external-storage/1.31"
- "status-success=ci/centos/k8s-e2e-external-storage/1.32"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.30"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.31"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.32"
- "status-success=ci/centos/mini-e2e/k8s-1.30"
- "status-success=ci/centos/mini-e2e/k8s-1.31"
- "status-success=ci/centos/mini-e2e/k8s-1.32"
- "status-success=ci/centos/upgrade-tests-cephfs"
- "status-success=ci/centos/upgrade-tests-rbd"
add mergify as a merge engine From now on, each PR will be merged automatically if: * there is no DNM label on the PR AND * the PR has at least one approuval AND * the travis CI successfully passed Closes: https://github.com/ceph/ceph-csi/issues/154 Signed-off-by: Sébastien Han <seb@redhat.com>
2019-01-31 18:03:31 +01:00
actions:
ci: move from merge action to queue action as mentioned in the below blog the support for strict mode and merge action will be done soon in mergify. This brings the change requested for the same. Ref# https://blog.mergify.com/strict-mode-deprecation/ Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
2022-01-10 15:33:25 +05:30
queue:
name: default
CI: Add Rule to auto merge PR 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 on the PR. The bot will merge the PR if it's having one approval and the label `ready-to-merge` Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
2020-05-15 13:55:09 +05:30
delete_head_branch: {}
ci: don't dismiss review if PR has not merged Pull requests are not going to be queued if at the same time the pull request review are dismiss Original-author: Mehdi ABAAKOUK <sileht@sileht.net> Signed-off-by: Niels de Vos <ndevos@redhat.com>
2022-01-11 19:41:51 +01:00
CI: Add Rule to auto merge PR 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 on the PR. The bot will merge the PR if it's having one approval and the label `ready-to-merge` Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
2020-05-15 13:55:09 +05:30
- name: automatic merge PR having ready-to-merge label
conditions:
ci: skip kube 1.25 check for devel branch Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2023-08-25 17:44:49 +05:30
- or:
- and:
ci: use regex comparing `~=` for `release-v*` branch checking It seems that `base=release-v*` does not match the `release-v3.10` branch for some reason. Maybe a Mergify update requires stricter checking of strings, and only allows the `~=` operator for regular expressions now? Regular expressions like `base~=^(devel)|(release-.+)$` seem to match for `release-3.10`, so let's use that notation everywhere. Signed-off-by: Niels de Vos <ndevos@ibm.com>
2023-12-01 10:14:41 +01:00
- base~=^(release-.+)$
ci: skip kube 1.25 check for devel branch Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2023-08-25 17:44:49 +05:30
- label!=DNM
- label=ready-to-merge
- "approved-reviews-by=@ceph/ceph-csi-maintainers"
- "status-success=codespell"
- "status-success=multi-arch-build"
- "status-success=go-test"
- "status-success=golangci-lint"
- "status-success=commitlint"
- "status-success=mod-check"
- "status-success=lint-extras"
- "#changes-requested-reviews-by=0"
ci: add test for uncommitted changes in deploy directory added test for uncommitted changes in deploy directory under go-test GH action. Also, created a new make target named `make check-deploy-committed` that can be used to verify the uncommitted changes. Signed-off-by: Nikhil-Ladha <nikhilladha1999@gmail.com>
2024-08-13 12:29:40 +05:30
- "status-success=uncommitted-code-check"
ci: skip kube 1.25 check for devel branch Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2023-08-25 17:44:49 +05:30
- "status-success=DCO"
ci: update rule for ci/skip/e2e updates mergify rules to handle ci/skip/e2e label Signed-off-by: ShravaniVangur <shravanivangur@gmail.com>
2025-03-11 14:39:25 +05:30
- or:
- label=ci/skip/e2e
- and:
- "status-success=ci/centos/k8s-e2e-external-storage/1.29"
- "status-success=ci/centos/k8s-e2e-external-storage/1.30"
- "status-success=ci/centos/k8s-e2e-external-storage/1.31"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.29"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.30"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.31"
- "status-success=ci/centos/mini-e2e/k8s-1.29"
- "status-success=ci/centos/mini-e2e/k8s-1.30"
- "status-success=ci/centos/mini-e2e/k8s-1.31"
- "status-success=ci/centos/upgrade-tests-cephfs"
- "status-success=ci/centos/upgrade-tests-rbd"
ci: update the merfigy rule to exclude k8s 1.25 This commit excludes the k8s 1.25 check from the mergify rules for ready-to-merge label Signed-off-by: Yati Padia <ypadia@redhat.com>
2024-02-20 15:03:45 +05:30
- and:
ci: update mergify rules updating mergify rules to drop 3.11 and add 3.13 support. Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
2024-12-03 08:13:02 +01:00
- base=release-v3.12
ci: update the merfigy rule to exclude k8s 1.25 This commit excludes the k8s 1.25 check from the mergify rules for ready-to-merge label Signed-off-by: Yati Padia <ypadia@redhat.com>
2024-02-20 15:03:45 +05:30
- label!=DNM
- label=ready-to-merge
- "approved-reviews-by=@ceph/ceph-csi-maintainers"
- "status-success=codespell"
- "status-success=multi-arch-build"
- "status-success=go-test"
- "status-success=golangci-lint"
- "status-success=commitlint"
- "status-success=mod-check"
- "status-success=lint-extras"
- "#changes-requested-reviews-by=0"
- "status-success=DCO"
ci: update rule for ci/skip/e2e updates mergify rules to handle ci/skip/e2e label Signed-off-by: ShravaniVangur <shravanivangur@gmail.com>
2025-03-11 14:39:25 +05:30
- or:
- label=ci/skip/e2e
- and:
- "status-success=ci/centos/k8s-e2e-external-storage/1.29"
- "status-success=ci/centos/k8s-e2e-external-storage/1.30"
- "status-success=ci/centos/k8s-e2e-external-storage/1.31"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.29"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.30"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.31"
- "status-success=ci/centos/mini-e2e/k8s-1.29"
- "status-success=ci/centos/mini-e2e/k8s-1.30"
- "status-success=ci/centos/mini-e2e/k8s-1.31"
- "status-success=ci/centos/upgrade-tests-cephfs"
- "status-success=ci/centos/upgrade-tests-rbd"
ci: add mergify rules for release-v3.2 added mergify rules for backporting and for auto merging the PR. Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
2020-12-08 12:32:27 +05:30
actions:
ci: move from merge action to queue action as mentioned in the below blog the support for strict mode and merge action will be done soon in mergify. This brings the change requested for the same. Ref# https://blog.mergify.com/strict-mode-deprecation/ Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
2022-01-10 15:33:25 +05:30
queue:
name: default
ci: add mergify rules for release-v3.2 added mergify rules for backporting and for auto merging the PR. Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
2020-12-08 12:32:27 +05:30
delete_head_branch: {}
ci: automatically remove `ok-to-test` and set it when queuing a PR The `ok-to-test` label currently needs to be removed and re-added when a PR is rebased for re-queuing. It should be possible to automate this, by removing the `ok-to-test` label when a PR gets queued. It can automatically be added again when the PR has embarked the merge train. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2022-11-09 14:29:20 +01:00
ci: update mergify rules updating mergify rules to drop 3.11 and add 3.13 support. Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
2024-12-03 08:13:02 +01:00
- name: backport patches to release-v3.12 branch
ci: add mergify rules for release-v3.8 added mergify rules to backport PR to release-v3.8 branch. Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
2023-02-23 09:02:19 +01:00
conditions:
- base=devel
ci: update mergify rules updating mergify rules to drop 3.11 and add 3.13 support. Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
2024-12-03 08:13:02 +01:00
- label=backport-to-release-v3.12
ci: add mergify rules for release-v3.8 added mergify rules to backport PR to release-v3.8 branch. Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
2023-02-23 09:02:19 +01:00
actions:
backport:
branches:
ci: update mergify rules updating mergify rules to drop 3.11 and add 3.13 support. Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
2024-12-03 08:13:02 +01:00
- release-v3.12
ci: add mergify rules for release-v3.8 added mergify rules to backport PR to release-v3.8 branch. Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
2023-02-23 09:02:19 +01:00
ci: update mergify rules updating mergify rules to drop 3.11 and add 3.13 support. Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
2024-12-03 08:13:02 +01:00
- name: backport patches to release-v3.13 branch
ci: add mergify rules for release-v3.9 This commit adds mergify rules to backport PR to release-v3.9 branch. Signed-off-by: Rakshith R <rar@redhat.com>
2023-06-26 20:26:07 +05:30
conditions:
- base=devel
ci: update mergify rules updating mergify rules to drop 3.11 and add 3.13 support. Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
2024-12-03 08:13:02 +01:00
- label=backport-to-release-v3.13
ci: add mergify rules for release-v3.9 This commit adds mergify rules to backport PR to release-v3.9 branch. Signed-off-by: Rakshith R <rar@redhat.com>
2023-06-26 20:26:07 +05:30
actions:
backport:
branches:
ci: update mergify rules updating mergify rules to drop 3.11 and add 3.13 support. Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
2024-12-03 08:13:02 +01:00
- release-v3.13
ci: add mergify rules for release-v3.9 This commit adds mergify rules to backport PR to release-v3.9 branch. Signed-off-by: Rakshith R <rar@redhat.com>
2023-06-26 20:26:07 +05:30
ci: automatically merge PRs in ci/centos Merge PRs for the ci/centos branch when they have sufficient approvals and the tests have passed. Using the same rules as the master branch. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2020-05-27 11:43:08 +02:00
- name: remove outdated approvals on ci/centos
conditions:
- base=ci/centos
actions:
dismiss_reviews:
approved: true
changes_requested: false
ci: automatically remove `ok-to-test` and set it when queuing a PR The `ok-to-test` label currently needs to be removed and re-added when a PR is rebased for re-queuing. It should be possible to automate this, by removing the `ok-to-test` label when a PR gets queued. It can automatically be added again when the PR has embarked the merge train. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2022-11-09 14:29:20 +01:00
ci: automatically merge PRs in ci/centos Merge PRs for the ci/centos branch when they have sufficient approvals and the tests have passed. Using the same rules as the master branch. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2020-05-27 11:43:08 +02:00
- name: automatic merge on ci/centos
conditions:
- label!=DNM
- base=ci/centos
- "#approved-reviews-by>=2"
ci: update mergify rules to include teams updated mergify rules to consider the teams approval to merge a PR. more details at #2367 fixes #2367 Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
2021-08-25 15:10:02 +05:30
- "approved-reviews-by=@ceph/ceph-csi-contributors"
- "approved-reviews-by=@ceph/ceph-csi-maintainers"
ci: automatically merge PRs in ci/centos Merge PRs for the ci/centos branch when they have sufficient approvals and the tests have passed. Using the same rules as the master branch. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2020-05-27 11:43:08 +02:00
- "#changes-requested-reviews-by=0"
- "status-success=ci/centos/job-validation"
ci: require jjb-validate job to succeed for ci/centos branch The jjb-validate job can not be run in parallel, so it may fail when multiple PRs for the ci/centos branch are sent. However, the ci/centos branch is not very active, so problems should be minimal. In case of problems, leave the following comment in the PR and the job should restart: /retest ci/centos/jjb-validate See-also: #1273 Signed-off-by: Niels de Vos <ndevos@redhat.com>
2020-07-24 16:19:42 +02:00
- "status-success=ci/centos/jjb-validate"
ci: automatically merge PRs in ci/centos Merge PRs for the ci/centos branch when they have sufficient approvals and the tests have passed. Using the same rules as the master branch. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2020-05-27 11:43:08 +02:00
- "status-success=DCO"
actions:
ci: move from merge action to queue action as mentioned in the below blog the support for strict mode and merge action will be done soon in mergify. This brings the change requested for the same. Ref# https://blog.mergify.com/strict-mode-deprecation/ Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
2022-01-10 15:33:25 +05:30
queue:
name: default
ci: automatically merge PRs in ci/centos Merge PRs for the ci/centos branch when they have sufficient approvals and the tests have passed. Using the same rules as the master branch. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2020-05-27 11:43:08 +02:00
delete_head_branch: {}
ci: automatically remove `ok-to-test` and set it when queuing a PR The `ok-to-test` label currently needs to be removed and re-added when a PR is rebased for re-queuing. It should be possible to automate this, by removing the `ok-to-test` label when a PR gets queued. It can automatically be added again when the PR has embarked the merge train. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2022-11-09 14:29:20 +01:00
ci: automatically merge PRs in ci/centos Merge PRs for the ci/centos branch when they have sufficient approvals and the tests have passed. Using the same rules as the master branch. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2020-05-27 11:43:08 +02:00
- name: automatic merge PR having ready-to-merge label on ci/centos
conditions:
- label!=DNM
- label=ready-to-merge
- base=ci/centos
ci: update mergify rules to include teams updated mergify rules to consider the teams approval to merge a PR. more details at #2367 fixes #2367 Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
2021-08-25 15:10:02 +05:30
- "approved-reviews-by=@ceph/ceph-csi-maintainers"
ci: automatically merge PRs in ci/centos Merge PRs for the ci/centos branch when they have sufficient approvals and the tests have passed. Using the same rules as the master branch. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2020-05-27 11:43:08 +02:00
- "#changes-requested-reviews-by=0"
- "status-success=ci/centos/job-validation"
ci: require jjb-validate job to succeed for ci/centos branch The jjb-validate job can not be run in parallel, so it may fail when multiple PRs for the ci/centos branch are sent. However, the ci/centos branch is not very active, so problems should be minimal. In case of problems, leave the following comment in the PR and the job should restart: /retest ci/centos/jjb-validate See-also: #1273 Signed-off-by: Niels de Vos <ndevos@redhat.com>
2020-07-24 16:19:42 +02:00
- "status-success=ci/centos/jjb-validate"
ci: automatically merge PRs in ci/centos Merge PRs for the ci/centos branch when they have sufficient approvals and the tests have passed. Using the same rules as the master branch. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2020-05-27 11:43:08 +02:00
- "status-success=DCO"
actions:
ci: move from merge action to queue action as mentioned in the below blog the support for strict mode and merge action will be done soon in mergify. This brings the change requested for the same. Ref# https://blog.mergify.com/strict-mode-deprecation/ Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
2022-01-10 15:33:25 +05:30
queue:
name: default
ci: automatically merge PRs in ci/centos Merge PRs for the ci/centos branch when they have sufficient approvals and the tests have passed. Using the same rules as the master branch. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2020-05-27 11:43:08 +02:00
delete_head_branch: {}
ci: automatically remove `ok-to-test` and set it when queuing a PR The `ok-to-test` label currently needs to be removed and re-added when a PR is rebased for re-queuing. It should be possible to automate this, by removing the `ok-to-test` label when a PR gets queued. It can automatically be added again when the PR has embarked the merge train. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2022-11-09 14:29:20 +01:00
ci: use mergify to add labels to PRs Adding labels to Pull-Requests can be done by Mergify. It is very useful to filter PRs on their labels so that experts in certain areas can identify PRs to review. Adding labels is currently a complete manual process, this adds some automation for it. There is no intention of it being complete, this is mostly for getting started and trying things out. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2021-05-05 13:59:06 +02:00
##
## Automatically set/remove labels
##
- name: title contains DNM
conditions:
- title~=DNM
actions:
label:
add:
- DNM
- name: title contains CephFS
conditions:
- "title~=cephfs: "
actions:
label:
add:
- component/cephfs
ci: add "component/nfs" label with Mergify "component/nfs" has been added to the labels in the repository, and Mergify should be able to add that to PRs. Updates: #2913 Signed-off-by: Niels de Vos <ndevos@redhat.com>
2022-03-17 11:31:00 +01:00
- name: title contains NFS
conditions:
- "title~=nfs: "
actions:
label:
add:
- component/nfs
ci: use mergify to add labels to PRs Adding labels to Pull-Requests can be done by Mergify. It is very useful to filter PRs on their labels so that experts in certain areas can identify PRs to review. Adding labels is currently a complete manual process, this adds some automation for it. There is no intention of it being complete, this is mostly for getting started and trying things out. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2021-05-05 13:59:06 +02:00
- name: title contains RBD
conditions:
- "title~=rbd: "
actions:
label:
add:
- component/rbd
ci: update mergify config for labelling PRs When the configuration for Mergify itself gets updated, there is not need to run the e2e tests. It seems that the `(ci)` part of matching a title for ci/testing PRs would match partial words like 'capacity'. This is not intended, so rephrasing the regex and adding `e2e` as match too. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2021-05-06 08:52:38 +02:00
- name: title contains CI, testing or e2e
ci: use mergify to add labels to PRs Adding labels to Pull-Requests can be done by Mergify. It is very useful to filter PRs on their labels so that experts in certain areas can identify PRs to review. Adding labels is currently a complete manual process, this adds some automation for it. There is no intention of it being complete, this is mostly for getting started and trying things out. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2021-05-05 13:59:06 +02:00
conditions:
ci: update mergify config for labelling PRs When the configuration for Mergify itself gets updated, there is not need to run the e2e tests. It seems that the `(ci)` part of matching a title for ci/testing PRs would match partial words like 'capacity'. This is not intended, so rephrasing the regex and adding `e2e` as match too. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2021-05-06 08:52:38 +02:00
- "title~=(ci: )|(testing: )|(e2e)"
ci: use mergify to add labels to PRs Adding labels to Pull-Requests can be done by Mergify. It is very useful to filter PRs on their labels so that experts in certain areas can identify PRs to review. Adding labels is currently a complete manual process, this adds some automation for it. There is no intention of it being complete, this is mostly for getting started and trying things out. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2021-05-05 13:59:06 +02:00
actions:
label:
add:
- component/testing
- name: title contains Helm
conditions:
- title~=helm
actions:
label:
add:
- component/deployment
- name: title contains rebase
conditions:
- "title~=rebase: "
actions:
label:
add:
- rebase
ci: have mergify set the component/build label on PRs Quite a few PRs have the `build:` prefix. It would be good to teach Mergify to set the label for those. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2021-05-14 16:41:24 +02:00
- name: title contains build
conditions:
- "title~=build: "
actions:
label:
add:
- component/build
ci: use mergify to add labels to PRs Adding labels to Pull-Requests can be done by Mergify. It is very useful to filter PRs on their labels so that experts in certain areas can identify PRs to review. Adding labels is currently a complete manual process, this adds some automation for it. There is no intention of it being complete, this is mostly for getting started and trying things out. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2021-05-05 13:59:06 +02:00
- name: title indicates a bug fix
conditions:
- title~=(bug)|(fix)
actions:
label:
add:
- bug
- name: title contains cleanup
conditions:
- "title~=cleanup: "
actions:
label:
add:
- cleanup
- name: title contains doc
conditions:
- "title~=doc: "
actions:
label:
add:
- component/docs
- ci/skip/e2e
ci: skip mutli-arch-build for doc and mergify prs Signed-off-by: Rakshith R <rar@redhat.com>
2022-08-19 10:14:41 +05:30
- ci/skip/multi-arch-build
ci: update mergify config for labelling PRs When the configuration for Mergify itself gets updated, there is not need to run the e2e tests. It seems that the `(ci)` part of matching a title for ci/testing PRs would match partial words like 'capacity'. This is not intended, so rephrasing the regex and adding `e2e` as match too. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2021-05-06 08:52:38 +02:00
- name: title contains Mergify
conditions:
ci: ignore case when matching Mergify config update PRs that contain `mergify` or `Mergify` in the subject should both match the rule to add labels. The regular expressions can include `(?i)` to make the matching case-insensitive. See-also: https://docs.mergify.com/configuration/#regular-expressions Signed-off-by: Niels de Vos <ndevos@redhat.com>
2021-11-23 09:13:05 +01:00
- "title~=(?i)mergify"
ci: update mergify config for labelling PRs When the configuration for Mergify itself gets updated, there is not need to run the e2e tests. It seems that the `(ci)` part of matching a title for ci/testing PRs would match partial words like 'capacity'. This is not intended, so rephrasing the regex and adding `e2e` as match too. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2021-05-06 08:52:38 +02:00
actions:
label:
add:
- Repo activity
- ci/skip/e2e
ci: skip mutli-arch-build for doc and mergify prs Signed-off-by: Rakshith R <rar@redhat.com>
2022-08-19 10:14:41 +05:30
- ci/skip/multi-arch-build
ci: detect `[skip ci]` in PR descriptions and prevent breakage When Jenkins jobs are started by a comment, and if the PR contains `[skip ci]` in the description, Jenkins does not run the requested job, nor set a status for the job in the PR. This causes Mergify to add the `ok-to-test` label again, instructing a GitHub Action to add comments to start jobs in Jenkins. Once all comments have been posted, the `ok-to-test` label is removed. Mergify then notices that the jobs were not run, and adds the `ok-to-test` label again.... Endlessly looping of adding the label, commenting and removing the label as a result. By reporting the brokenness of the PR description and marking the PR as Draft, the looping is prevented. Signed-off-by: Niels de Vos <ndevos@ibm.com>
2024-08-07 09:54:25 +02:00
# A [skip ci] in the PR description prevents Jenkins jobs from running, mark
# the PR as Draft so that CI jobs do not automatically run anymore.
- name: detect [skip ci] in the PR description
conditions:
ci: prevent incorrect pattern matching for `skipping ci` command Mergify matches `body-raw` as regular expression, but that makes it difficult (if not impossible) to match the `[` in a string. Fixes: #4751 Signed-off-by: Niels de Vos <ndevos@ibm.com>
2024-08-09 12:22:34 +02:00
# this should be \[skip\W+ci\], but Mergify does not accept that
- "body-raw~=skip ci"
ci: detect `[skip ci]` in PR descriptions and prevent breakage When Jenkins jobs are started by a comment, and if the PR contains `[skip ci]` in the description, Jenkins does not run the requested job, nor set a status for the job in the PR. This causes Mergify to add the `ok-to-test` label again, instructing a GitHub Action to add comments to start jobs in Jenkins. Once all comments have been posted, the `ok-to-test` label is removed. Mergify then notices that the jobs were not run, and adds the `ok-to-test` label again.... Endlessly looping of adding the label, commenting and removing the label as a result. By reporting the brokenness of the PR description and marking the PR as Draft, the looping is prevented. Signed-off-by: Niels de Vos <ndevos@ibm.com>
2024-08-07 09:54:25 +02:00
actions:
edit:
draft: true
comment:
ci: update mergify config to replace,remove deprecated attributes update mergify config to remove, replace the deprecated attributes. Signed-off-by: Nikhil-Ladha <nikhilladha1999@gmail.com>
2024-08-21 10:21:47 +05:30
# yamllint disable-line rule:truthy rule:line-length
message: "The PR description contains the unsupported `[skip ci]` command, please update the description and mark the PR ready for review again."
Reference in New Issue Copy Permalink