Skip to content

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Aug 4, 2025

No description provided.

@github-actions
Copy link
Contributor Author

github-actions bot commented Aug 4, 2025

/approve

@bert-e
Copy link
Contributor

bert-e commented Aug 4, 2025

Hello github-actions[bot],

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
/bypass_build_status Bypass the build and test status
/bypass_commit_size Bypass the check on the size of the changeset TBA
/bypass_incompatible_branch Bypass the check on the source branch prefix
/bypass_jira_check Bypass the Jira issue check
/bypass_peer_approval Bypass the pull request peers' approval
/bypass_leader_approval Bypass the pull request leaders' approval
/approve Instruct Bert-E that the author has approved the pull request. ✍️
/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.

The following options are set: bypass_author_approval, bypass_jira_check

@bert-e
Copy link
Contributor

bert-e commented Aug 4, 2025

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

The following options are set: approve, bypass_author_approval, bypass_jira_check

@bert-e
Copy link
Contributor

bert-e commented Dec 5, 2025

Branches have diverged

This pull request's source branch feature/merge-131.0.0-alpha.2-tag has diverged from
development/131.0 by more than 50 commits.

To avoid any integration risks, please re-synchronize them using one of the
following solutions:

  • Merge origin/development/131.0 into feature/merge-131.0.0-alpha.2-tag
  • Rebase feature/merge-131.0.0-alpha.2-tag onto origin/development/131.0

Note: If you choose to rebase, you may have to ask me to rebuild
integration branches using the reset command.

The following options are set: approve, bypass_author_approval, bypass_jira_check

@TeddyAndrieux TeddyAndrieux force-pushed the feature/merge-131.0.0-alpha.2-tag branch from 8732408 to 465ed40 Compare December 5, 2025 18:25
@TeddyAndrieux TeddyAndrieux reopened this Dec 5, 2025
@bert-e
Copy link
Contributor

bert-e commented Dec 5, 2025

Integration data created

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

The following branches will NOT be impacted:

  • development/123.0
  • development/124.0
  • development/124.1
  • development/125.0
  • development/126.0
  • development/127.0
  • development/128.0
  • development/129.0
  • development/130.0
  • development/2.0
  • development/2.1
  • development/2.10
  • development/2.11
  • development/2.2
  • development/2.3
  • development/2.4
  • development/2.5
  • development/2.6
  • development/2.7
  • development/2.8
  • development/2.9

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, bypass_author_approval, bypass_jira_check

@bert-e
Copy link
Contributor

bert-e commented Dec 5, 2025

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • one peer

Peer approvals must include at least 1 approval from the following list:

The following options are set: approve, bypass_author_approval, bypass_jira_check

@bert-e
Copy link
Contributor

bert-e commented Dec 5, 2025

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

  • ✔️ development/131.0

  • ✔️ development/132.0

The following branches have NOT changed:

  • development/123.0
  • development/124.0
  • development/124.1
  • development/125.0
  • development/126.0
  • development/127.0
  • development/128.0
  • development/129.0
  • development/130.0
  • development/2.0
  • development/2.1
  • development/2.10
  • development/2.11
  • development/2.2
  • development/2.3
  • development/2.4
  • development/2.5
  • development/2.6
  • development/2.7
  • development/2.8
  • development/2.9

Please check the status of the associated issue MERGE-131.

Goodbye github-actions[bot].

The following options are set: approve, bypass_author_approval, bypass_jira_check

@bert-e bert-e merged commit ae9c54d into development/131.0 Dec 5, 2025
26 checks passed
@bert-e bert-e deleted the feature/merge-131.0.0-alpha.2-tag branch December 5, 2025 18:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants