Skip to content

Conversation

@DarkIsDude
Copy link
Contributor

What does this PR do, and why do we need it?

Which issue does this PR fix?

Fixes ZENKO-XXXX.

Special notes for your reviewers:

@DarkIsDude DarkIsDude self-assigned this Dec 2, 2025
@bert-e
Copy link
Contributor

bert-e commented Dec 2, 2025

Hello darkisdude,

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.

@bert-e
Copy link
Contributor

bert-e commented Dec 2, 2025

Missing Jira issue

It is mandatory to specify a Jira issue in the source branch name
in order to merge into development/2.13. The issue key must follow
the prefix of the branch.

I could not find such an issue in feature/test-bump-penieve.

@DarkIsDude DarkIsDude force-pushed the feature/test-bump-penieve branch from d68d232 to 91d4fe2 Compare December 3, 2025 09:21
@DarkIsDude DarkIsDude force-pushed the feature/test-bump-penieve branch from 91d4fe2 to ab789e6 Compare December 3, 2025 11:04
@DarkIsDude DarkIsDude closed this Dec 3, 2025
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