Zenko icon indicating copy to clipboard operation
Zenko copied to clipboard

Deploy second zenko for PRA

Open KillianG opened this issue 1 year ago • 2 comments

Issue: ZENKO-4772

KillianG avatar Jun 04 '24 15:06 KillianG

Hello killiang,

My role is to assist you with the merge of this pull request. Please type @bert-e help to get information on this process, or consult the user documentation.

Available options
name description privileged authored
/after_pull_request Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval Bypass the pull request author's approval :star:
/bypass_build_status Bypass the build and test status :star:
/bypass_commit_size Bypass the check on the size of the changeset TBA :star:
/bypass_incompatible_branch Bypass the check on the source branch prefix :star:
/bypass_jira_check Bypass the Jira issue check :star:
/bypass_peer_approval Bypass the pull request peers' approval :star:
/bypass_leader_approval Bypass the pull request leaders' approval :star:
/approve Instruct Bert-E that the author has approved the pull request. :writing_hand:
/create_pull_requests Allow the creation of integration pull requests.
/create_integration_branches Allow the creation of integration branches.
/no_octopus Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity Change review acceptance criteria from one reviewer at least to all reviewers
/wait Instruct Bert-E not to run until further notice.
Available commands
name description privileged
/help Print Bert-E's manual in the pull request.
/status Print Bert-E's current status in the pull request TBA
/clear Remove all comments from Bert-E from the history TBA
/retry Re-start a fresh build TBA
/build Re-start a fresh build TBA
/force_reset Delete integration branches & pull requests, and restart merge process from the beginning.
/reset Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

bert-e avatar Jun 04 '24 15:06 bert-e

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically create the integration branches.

bert-e avatar Jul 03 '24 13:07 bert-e

/approve

KillianG avatar Jul 09 '24 15:07 KillianG

Integration data created

I have created the integration data for the additional destination branches.

The following branches will NOT be impacted:

  • development/2.5

You can set option create_pull_requests if you need me to create integration pull requests in addition to integration branches, with:

@bert-e create_pull_requests

The following options are set: approve

bert-e avatar Jul 09 '24 15:07 bert-e

/after_pull_request=2101

francoisferrand avatar Jul 10 '24 10:07 francoisferrand

Waiting for other pull request(s)

The current pull request is locked by the after_pull_request option.

In order for me to merge this pull request, run the following actions first:

:arrow_right: Merge the OPEN pull request:

  • pull request #2101

Alternatively, delete all the after_pull_request comments from this pull request.

The following options are set: after_pull_request, approve

bert-e avatar Jul 10 '24 10:07 bert-e

In the queue

The changeset has received all authorizations and has been added to the relevant queue(s). The queue(s) will be merged in the target development branch(es) as soon as builds have passed.

The changeset will be merged in:

  • :heavy_check_mark: development/2.6

  • :heavy_check_mark: development/2.7

  • :heavy_check_mark: development/2.8

  • :heavy_check_mark: development/2.9

The following branches will NOT be impacted:

  • development/2.5

There is no action required on your side. You will be notified here once the changeset has been merged. In the unlikely event that the changeset fails permanently on the queue, a member of the admin team will contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

  • Any commit you add on the source branch will trigger a new cycle after the current queue is merged.
  • Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a member of the admin team now.

The following options are set: after_pull_request, approve

bert-e avatar Jul 11 '24 07:07 bert-e

I have successfully merged the changeset of this pull request into targetted development branches:

  • :heavy_check_mark: development/2.6

  • :heavy_check_mark: development/2.7

  • :heavy_check_mark: development/2.8

  • :heavy_check_mark: development/2.9

The following branches have NOT changed:

  • development/2.5

Please check the status of the associated issue ZENKO-4772.

Goodbye killiang.

bert-e avatar Jul 12 '24 10:07 bert-e