Closed Kerkesni closed 1 year ago
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.
Status report is not available.
The following approvals are needed before I can proceed with the merge:
the author
2 peers
The Fix Version/s
in issue BB-269 contains:
8.5.4
Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:
8.5.4
8.6.0
Please check the Fix Version/s
of BB-269, or the target
branch of this pull request.
The Fix Version/s
in issue BB-269 contains:
8.5.4
Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:
8.5.4
8.6.1
Please check the Fix Version/s
of BB-269, or the target
branch of this pull request.
I have created the integration data for the additional destination branches.
bugfix/BB-269
into
development/8.5
development/8.6
The following branches will NOT be impacted:
development/7.10
development/7.4
development/8.3
development/8.4
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 approvals are needed before I can proceed with the merge:
the author
2 peers
Merge commit #cffbd1f344a8f2a98a965bd1e01ce1d4ca3c934c on the integration branch
w/8.6/bugfix/BB-269
is merging a branch which is neither the current
branch bugfix/BB-269
nor the development branch
development/8.6
.
It is likely due to a rebase of the branch bugfix/BB-269
and the
merge is not possible until all related w/*
branches are deleted or updated.
Please use the reset
command to have me reinitialize these branches.
/reset
I have successfully deleted this pull request's integration branches.
I have created the integration data for the additional destination branches.
bugfix/BB-269
into
development/8.5
development/8.6
The following branches will NOT be impacted:
development/7.10
development/7.4
development/8.3
development/8.4
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 approvals are needed before I can proceed with the merge:
the author
2 peers
/approve
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/8.5
:heavy_check_mark: development/8.6
The following branches will NOT be impacted:
development/7.10
development/7.4
development/8.3
development/8.4
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.
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: approve
I have successfully merged the changeset of this pull request into targetted development branches:
:heavy_check_mark: development/8.5
:heavy_check_mark: development/8.6
The following branches have NOT changed:
development/7.10
development/7.4
development/8.3
development/8.4
Please check the status of the associated issue BB-269.
Goodbye kerkesni.
Issue: BB-269
Replication has special code to handle replication of tags: in that case, it will not replicate the object again, but simply update the tags on the target object.
However, in the (unlikely) case where that tag update fails, the datastore version id will be reset when the entry is put in the replay queue:
Consequently, the replay-processor would trigger a full replication of the object, and the data will be copied again.