mirrors/ceph-csi
1
0
Fork 0
mirror of https://github.com/ceph/ceph-csi.git synced 2024-11-14 02:10:21 +00:00
Code Issues Packages Projects Releases Wiki Activity
0a82f17671
ceph-csi/.mergify.yml

536 lines
21 KiB
YAML
Raw Normal View History

Fix yaml lint error in mergify Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
2019-03-22 05:27:56 +00:00
---
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 07:46:47 +00:00
defaults:
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 10:03:25 +00:00
queue:
cleanup: update mergify.yml to remove bot_account option Mergify.io has removed bot_account from its free open source plan. This commit removes bot_account option from comment, merge and rebase actions default and documenting the implications going forward. Signed-off-by: Rakshith R <rar@redhat.com>
2021-04-15 05:57:32 +00:00
# merge_bot_account: ceph-csi-bot #mergify[bot] will be merging prs.
# update_bot_account: ceph-csi-bot #mergify will randomly pick and use
# credentials of users with write access to repo to rebase prs.
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 10:03:25 +00:00
name: default
build: move mergify/merge options to defaults section Signed-off-by: Niels de Vos <ndevos@redhat.com>
2021-03-01 07:51:03 +00:00
method: rebase
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 10:03:25 +00:00
update_method: rebase
ci: `bot_account` is not available for our Mergify usage `bot_account` is a feature that is part of the paid subscription. The Ceph organization does not have that. Mergify will use the author of the PR for rebasing by default. This isn't very nice, but we can't change it at the moment. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2023-02-01 12:58:25 +00:00
# For rebasing Mergify uses the author of the PR. Ideally we use the
# ceph-csi-bot for that, but this is a feature that needs a paid
# subscription.
#
# rebase:
ci: use ceph-csi-bot for Mergify actions The `bot_account` option was not part of the Open Source plan, but now it is. When Mergify rebases PRs, it sometimes leaves the following message: ``` This pull request got rebased on behalf of a random user of the organization. This behavior will change on the 1st February 2023, Mergify will pick the author of the pull request instead. To get the future behavior now, you can configure bot_account options (e.g.: bot_account: { author } or update_bot_account: { author }. Or you can create a dedicated github account for squash and rebase operations, and use it in different bot_account options. ``` It is clearer for everyone when the Ceph-CSI Bot is used for automated actions. Contributers might get confused why the PR was updated in their name, without them doing anything. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2023-01-31 08:35:41 +00:00
# Use ceph-csi-bot for rebasing, not the account of the PR owner.
ci: `bot_account` is not available for our Mergify usage `bot_account` is a feature that is part of the paid subscription. The Ceph organization does not have that. Mergify will use the author of the PR for rebasing by default. This isn't very nice, but we can't change it at the moment. Signed-off-by: Niels de Vos <ndevos@redhat.com>
2023-02-01 12:58:25 +00:00
# bot_account: ceph-csi-bot
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 10:03:25 +00:00
ci: allow Mergify to merge PRs that modify the mergify configuration The new `allow_merging_configuration_change` option can be enabled to > Allow merging Mergify configuration change. Which is useful for a more automated process when preparing for a release. See-also: https://docs.mergify.com/workflow/actions/merge/#parameters Signed-off-by: Niels de Vos <ndevos@ibm.com>
2023-11-30 09:27:23 +00:00
# by default Mergify requires manual merging of PRs that modify its own
# configuration (this file), allowing this makes it easier to prepare for
# releases (new branches added here)
allow_merging_configuration_change: true
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 10:03:25 +00:00
queue_rules:
- name: default
conditions:
# 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 09:14:41 +00: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 10:03:25 +00:00
- "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: the release-v3.10 branch needs Kubernetes 1.28 jobs With Ceph-CSI v3.10 we do not test Kubernetes 1.25 anymore, and we expect Kubernetes 1.28 to be used. Signed-off-by: Niels de Vos <ndevos@ibm.com>
2023-11-30 20:14:27 +00:00
- "status-success=ci/centos/k8s-e2e-external-storage/1.26"
- "status-success=ci/centos/k8s-e2e-external-storage/1.27"
- "status-success=ci/centos/k8s-e2e-external-storage/1.28"
ci: update mergify rules for release branches Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2024-01-03 17:55:40 +00:00
- "status-success=ci/centos/k8s-e2e-external-storage/1.29"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.26"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.27"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.28"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.29"
- "status-success=ci/centos/mini-e2e/k8s-1.26"
- "status-success=ci/centos/mini-e2e/k8s-1.27"
- "status-success=ci/centos/mini-e2e/k8s-1.28"
- "status-success=ci/centos/mini-e2e/k8s-1.29"
- "status-success=ci/centos/upgrade-tests-cephfs"
- "status-success=ci/centos/upgrade-tests-rbd"
- and:
- base=release-v3.10
- "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=ci/centos/k8s-e2e-external-storage/1.26"
- "status-success=ci/centos/k8s-e2e-external-storage/1.27"
- "status-success=ci/centos/k8s-e2e-external-storage/1.28"
ci: the release-v3.10 branch needs Kubernetes 1.28 jobs With Ceph-CSI v3.10 we do not test Kubernetes 1.25 anymore, and we expect Kubernetes 1.28 to be used. Signed-off-by: Niels de Vos <ndevos@ibm.com>
2023-11-30 20:14:27 +00:00
- "status-success=ci/centos/mini-e2e-helm/k8s-1.26"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.27"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.28"
- "status-success=ci/centos/mini-e2e/k8s-1.26"
- "status-success=ci/centos/mini-e2e/k8s-1.27"
- "status-success=ci/centos/mini-e2e/k8s-1.28"
- "status-success=ci/centos/upgrade-tests-cephfs"
- "status-success=ci/centos/upgrade-tests-rbd"
- and:
- base=release-v3.9
- "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: consider kubernetes 1.25 for tests As we have successful runs with kubernetes 1.25 Marking is as default for CI jobs and required for merging PR. Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
2022-10-27 06:29:59 +00:00
- "status-success=ci/centos/k8s-e2e-external-storage/1.25"
ci: update mergify rules for Kubernetes 1.26 removed mergify rules for Kubernetes 1.23 and update the rules to consider Kubernetes 1.26 Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
2023-02-23 07:59:36 +00:00
- "status-success=ci/centos/k8s-e2e-external-storage/1.26"
ci: update mergify rules for kubernetes 1.27 Signed-off-by: riya-singhal31 <rsinghal@redhat.com>
2023-04-12 08:23:43 +00:00
- "status-success=ci/centos/k8s-e2e-external-storage/1.27"
ci: consider kubernetes 1.25 for tests As we have successful runs with kubernetes 1.25 Marking is as default for CI jobs and required for merging PR. Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
2022-10-27 06:29:59 +00:00
- "status-success=ci/centos/mini-e2e-helm/k8s-1.25"
ci: update mergify rules for Kubernetes 1.26 removed mergify rules for Kubernetes 1.23 and update the rules to consider Kubernetes 1.26 Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
2023-02-23 07:59:36 +00:00
- "status-success=ci/centos/mini-e2e-helm/k8s-1.26"
ci: update mergify rules for kubernetes 1.27 Signed-off-by: riya-singhal31 <rsinghal@redhat.com>
2023-04-12 08:23:43 +00:00
- "status-success=ci/centos/mini-e2e-helm/k8s-1.27"
ci: consider kubernetes 1.25 for tests As we have successful runs with kubernetes 1.25 Marking is as default for CI jobs and required for merging PR. Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
2022-10-27 06:29:59 +00:00
- "status-success=ci/centos/mini-e2e/k8s-1.25"
ci: update mergify rules for Kubernetes 1.26 removed mergify rules for Kubernetes 1.23 and update the rules to consider Kubernetes 1.26 Signed-off-by: Madhu Rajanna <madhupr007@gmail.com>
2023-02-23 07:59:36 +00:00
- "status-success=ci/centos/mini-e2e/k8s-1.26"
ci: update mergify rules for kubernetes 1.27 Signed-off-by: riya-singhal31 <rsinghal@redhat.com>
2023-04-12 08:23:43 +00:00
- "status-success=ci/centos/mini-e2e/k8s-1.27"
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 10:03:25 +00:00
- "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 12:14:49 +00:00
- 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"
- "status-success=ci/centos/k8s-e2e-external-storage/1.27"
- "status-success=ci/centos/k8s-e2e-external-storage/1.28"
ci: update mergify rules for kubernetes 1.29 Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2024-01-03 17:44:51 +00:00
- "status-success=ci/centos/k8s-e2e-external-storage/1.29"
ci: skip kube 1.25 check for devel branch Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2023-08-25 12:14:49 +00:00
- "status-success=ci/centos/mini-e2e-helm/k8s-1.27"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.28"
ci: update mergify rules for kubernetes 1.29 Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2024-01-03 17:44:51 +00:00
- "status-success=ci/centos/mini-e2e-helm/k8s-1.29"
ci: skip kube 1.25 check for devel branch Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2023-08-25 12:14:49 +00:00
- "status-success=ci/centos/mini-e2e/k8s-1.27"
- "status-success=ci/centos/mini-e2e/k8s-1.28"
ci: update mergify rules for kubernetes 1.29 Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2024-01-03 17:44:51 +00:00
- "status-success=ci/centos/mini-e2e/k8s-1.29"
ci: skip kube 1.25 check for devel branch Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2023-08-25 12:14:49 +00:00
- "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 10:03:25 +00:00
- and:
- base=ci/centos
- "status-success=ci/centos/job-validation"
- "status-success=ci/centos/jjb-validate"
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 07:46:47 +00: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 17:03:31 +00: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 11:34:10 +00: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 13:29:20 +00:00
conditions:
- base~=^(devel)|(release-.+)$
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 15:59:35 +00: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 11:56:59 +00: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 11:34:10 +00: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 05:31:08 +00:00
- 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 13:29:20 +00: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 11:45:21 +00: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 08:30:32 +00: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 11:45:21 +00: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 13:29:20 +00: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 10:45:01 +00:00
- 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 06:27:59 +00: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 10:45:01 +00:00
actions:
comment:
# yamllint disable-line rule:truthy
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 13:29:20 +00: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 15:08:19 +00:00
- name: update dependencies by dependabot (skip commitlint)
conditions:
ci: skip kube 1.25 check for devel branch Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2023-08-25 12:14:49 +00:00
- or:
- and:
- author=dependabot[bot]
- 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 09:14:41 +00:00
- base~=^(release-.+)$
ci: skip kube 1.25 check for devel branch Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2023-08-25 12:14:49 +00:00
- "#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=ci/centos/k8s-e2e-external-storage/1.25"
- "status-success=ci/centos/k8s-e2e-external-storage/1.26"
- "status-success=ci/centos/k8s-e2e-external-storage/1.27"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.25"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.26"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.27"
- "status-success=ci/centos/mini-e2e/k8s-1.25"
- "status-success=ci/centos/mini-e2e/k8s-1.26"
- "status-success=ci/centos/mini-e2e/k8s-1.27"
- "status-success=ci/centos/upgrade-tests-cephfs"
- "status-success=ci/centos/upgrade-tests-rbd"
- "status-success=DCO"
- and:
- 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=ci/centos/k8s-e2e-external-storage/1.27"
- "status-success=ci/centos/k8s-e2e-external-storage/1.28"
ci: update mergify rules for kubernetes 1.29 Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2024-01-03 17:44:51 +00:00
- "status-success=ci/centos/k8s-e2e-external-storage/1.29"
ci: skip kube 1.25 check for devel branch Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2023-08-25 12:14:49 +00:00
- "status-success=ci/centos/mini-e2e-helm/k8s-1.27"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.28"
ci: update mergify rules for kubernetes 1.29 Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2024-01-03 17:44:51 +00:00
- "status-success=ci/centos/mini-e2e-helm/k8s-1.29"
ci: skip kube 1.25 check for devel branch Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2023-08-25 12:14:49 +00:00
- "status-success=ci/centos/mini-e2e/k8s-1.27"
- "status-success=ci/centos/mini-e2e/k8s-1.28"
ci: update mergify rules for kubernetes 1.29 Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2024-01-03 17:44:51 +00:00
- "status-success=ci/centos/mini-e2e/k8s-1.29"
ci: skip kube 1.25 check for devel branch Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2023-08-25 12:14:49 +00:00
- "status-success=ci/centos/upgrade-tests-cephfs"
- "status-success=ci/centos/upgrade-tests-rbd"
- "status-success=DCO"
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 15:08:19 +00: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 10:03:25 +00:00
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 15:08:19 +00: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 18:41:51 +00: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 17:03:31 +00: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 12:14:49 +00:00
- 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 09:14:41 +00:00
- base~=^(release-.+)$
ci: skip kube 1.25 check for devel branch Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2023-08-25 12:14:49 +00: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: 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 09:16:55 +00: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 17:55:40 +00:00
- "status-success=lint-extras"
- "status-success=mod-check"
- "status-success=multi-arch-build"
- "status-success=ci/centos/k8s-e2e-external-storage/1.26"
- "status-success=ci/centos/k8s-e2e-external-storage/1.27"
- "status-success=ci/centos/k8s-e2e-external-storage/1.28"
- "status-success=ci/centos/k8s-e2e-external-storage/1.29"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.26"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.27"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.28"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.29"
- "status-success=ci/centos/mini-e2e/k8s-1.26"
- "status-success=ci/centos/mini-e2e/k8s-1.27"
- "status-success=ci/centos/mini-e2e/k8s-1.28"
- "status-success=ci/centos/mini-e2e/k8s-1.29"
- "status-success=ci/centos/upgrade-tests-cephfs"
- "status-success=ci/centos/upgrade-tests-rbd"
- and:
- label!=DNM
- base=release-v3.10
- "#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=DCO"
- "status-success=codespell"
- "status-success=commitlint"
- "status-success=go-test"
- "status-success=golangci-lint"
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 09:16:55 +00:00
- "status-success=lint-extras"
- "status-success=mod-check"
- "status-success=multi-arch-build"
- "status-success=ci/centos/k8s-e2e-external-storage/1.26"
- "status-success=ci/centos/k8s-e2e-external-storage/1.27"
- "status-success=ci/centos/k8s-e2e-external-storage/1.28"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.26"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.27"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.28"
- "status-success=ci/centos/mini-e2e/k8s-1.26"
- "status-success=ci/centos/mini-e2e/k8s-1.27"
- "status-success=ci/centos/mini-e2e/k8s-1.28"
- "status-success=ci/centos/upgrade-tests-cephfs"
- "status-success=ci/centos/upgrade-tests-rbd"
- and:
- label!=DNM
- base=release-v3.9
- "#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 12:14:49 +00:00
- "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=ci/centos/k8s-e2e-external-storage/1.25"
- "status-success=ci/centos/k8s-e2e-external-storage/1.26"
- "status-success=ci/centos/k8s-e2e-external-storage/1.27"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.25"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.26"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.27"
- "status-success=ci/centos/mini-e2e/k8s-1.25"
- "status-success=ci/centos/mini-e2e/k8s-1.26"
- "status-success=ci/centos/mini-e2e/k8s-1.27"
- "status-success=ci/centos/upgrade-tests-cephfs"
- "status-success=ci/centos/upgrade-tests-rbd"
- "status-success=DCO"
- 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=ci/centos/k8s-e2e-external-storage/1.27"
- "status-success=ci/centos/k8s-e2e-external-storage/1.28"
ci: update mergify rules for kubernetes 1.29 Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2024-01-03 17:44:51 +00:00
- "status-success=ci/centos/k8s-e2e-external-storage/1.29"
ci: skip kube 1.25 check for devel branch Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2023-08-25 12:14:49 +00:00
- "status-success=ci/centos/mini-e2e-helm/k8s-1.27"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.28"
ci: update mergify rules for kubernetes 1.29 Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2024-01-03 17:44:51 +00:00
- "status-success=ci/centos/mini-e2e-helm/k8s-1.29"
ci: skip kube 1.25 check for devel branch Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2023-08-25 12:14:49 +00:00
- "status-success=ci/centos/mini-e2e/k8s-1.27"
- "status-success=ci/centos/mini-e2e/k8s-1.28"
ci: update mergify rules for kubernetes 1.29 Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2024-01-03 17:44:51 +00:00
- "status-success=ci/centos/mini-e2e/k8s-1.29"
ci: skip kube 1.25 check for devel branch Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2023-08-25 12:14:49 +00:00
- "status-success=ci/centos/upgrade-tests-cephfs"
- "status-success=ci/centos/upgrade-tests-rbd"
- "status-success=DCO"
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 17:03:31 +00: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 10:03:25 +00:00
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 08:25:09 +00: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 18:41:51 +00: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 08:25:09 +00:00
- 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 12:14:49 +00:00
- 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 09:14:41 +00:00
- base~=^(release-.+)$
ci: skip kube 1.25 check for devel branch Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2023-08-25 12:14:49 +00:00
- 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=ci/centos/k8s-e2e-external-storage/1.25"
- "status-success=ci/centos/k8s-e2e-external-storage/1.26"
- "status-success=ci/centos/k8s-e2e-external-storage/1.27"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.25"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.26"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.27"
- "status-success=ci/centos/mini-e2e/k8s-1.25"
- "status-success=ci/centos/mini-e2e/k8s-1.26"
- "status-success=ci/centos/mini-e2e/k8s-1.27"
- "status-success=ci/centos/upgrade-tests-cephfs"
- "status-success=ci/centos/upgrade-tests-rbd"
- "status-success=DCO"
- and:
- base=devel
- 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=ci/centos/k8s-e2e-external-storage/1.27"
- "status-success=ci/centos/k8s-e2e-external-storage/1.28"
ci: update mergify rules for kubernetes 1.29 Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2024-01-03 17:44:51 +00:00
- "status-success=ci/centos/k8s-e2e-external-storage/1.29"
ci: skip kube 1.25 check for devel branch Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2023-08-25 12:14:49 +00:00
- "status-success=ci/centos/mini-e2e-helm/k8s-1.27"
- "status-success=ci/centos/mini-e2e-helm/k8s-1.28"
ci: update mergify rules for kubernetes 1.29 Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2024-01-03 17:44:51 +00:00
- "status-success=ci/centos/mini-e2e-helm/k8s-1.29"
ci: skip kube 1.25 check for devel branch Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2023-08-25 12:14:49 +00:00
- "status-success=ci/centos/mini-e2e/k8s-1.27"
- "status-success=ci/centos/mini-e2e/k8s-1.28"
ci: update mergify rules for kubernetes 1.29 Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2024-01-03 17:44:51 +00:00
- "status-success=ci/centos/mini-e2e/k8s-1.29"
ci: skip kube 1.25 check for devel branch Signed-off-by: Riya Singhal <rsinghal@redhat.com>
2023-08-25 12:14:49 +00:00
- "status-success=ci/centos/upgrade-tests-cephfs"
- "status-success=ci/centos/upgrade-tests-rbd"
- "status-success=DCO"
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 07:02:27 +00: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 10:03:25 +00:00
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 07:02:27 +00: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 13:29:20 +00:00
ci: modify mergifyio rules for new release-v3.10 This commit adds support for v3.10 backports and removes support for v3.8 backports. Signed-off-by: Rakshith R <rar@redhat.com>
2023-11-29 10:51:35 +00:00
- name: backport patches to release-v3.9 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 08:02:19 +00:00
conditions:
- base=devel
ci: modify mergifyio rules for new release-v3.10 This commit adds support for v3.10 backports and removes support for v3.8 backports. Signed-off-by: Rakshith R <rar@redhat.com>
2023-11-29 10:51:35 +00:00
- label=backport-to-release-v3.9
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 08:02:19 +00:00
actions:
backport:
branches:
ci: modify mergifyio rules for new release-v3.10 This commit adds support for v3.10 backports and removes support for v3.8 backports. Signed-off-by: Rakshith R <rar@redhat.com>
2023-11-29 10:51:35 +00:00
- release-v3.9
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 08:02:19 +00:00
ci: modify mergifyio rules for new release-v3.10 This commit adds support for v3.10 backports and removes support for v3.8 backports. Signed-off-by: Rakshith R <rar@redhat.com>
2023-11-29 10:51:35 +00:00
- name: backport patches to release-v3.10 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 14:56:07 +00:00
conditions:
- base=devel
ci: modify mergifyio rules for new release-v3.10 This commit adds support for v3.10 backports and removes support for v3.8 backports. Signed-off-by: Rakshith R <rar@redhat.com>
2023-11-29 10:51:35 +00:00
- label=backport-to-release-v3.10
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 14:56:07 +00:00
actions:
backport:
branches:
ci: modify mergifyio rules for new release-v3.10 This commit adds support for v3.10 backports and removes support for v3.8 backports. Signed-off-by: Rakshith R <rar@redhat.com>
2023-11-29 10:51:35 +00:00
- release-v3.10
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 14:56:07 +00: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 09:43:08 +00: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 13:29:20 +00: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 09:43:08 +00: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 09:40:02 +00:00
- "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 09:43:08 +00: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 14:19:42 +00: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 09:43:08 +00: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 10:03:25 +00:00
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 09:43:08 +00: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 13:29:20 +00: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 09:43:08 +00: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 09:40:02 +00:00
- "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 09:43:08 +00: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 14:19:42 +00: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 09:43:08 +00: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 10:03:25 +00:00
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 09:43:08 +00: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 13:29:20 +00: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 11:59:06 +00: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 10:31:00 +00: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 11:59:06 +00: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 06:52:38 +00: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 11:59:06 +00: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 06:52:38 +00: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 11:59:06 +00: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 14:41:24 +00: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 11:59:06 +00: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 04:44:41 +00:00
- 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 06:52:38 +00: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 08:13:05 +00: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 06:52:38 +00: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 04:44:41 +00:00
- ci/skip/multi-arch-build
Reference in New Issue Copy Permalink