Closed bernhardkaindl closed 3 weeks ago
Attention: Patch coverage is 92.78810%
with 97 lines
in your changes missing coverage. Please review.
emm, am I confused, why is this merging into master?
Thanks! Fixed the target branch to feature/py3
.
I did the merge again and compared it with the PR/merge branch - it should be ok:
# fetch latest git:
git remote -v|grep origin
origin git@github.com:xapi-project/xen-api.git (fetch)
origin git@github.com:xapi-project/xen-api.git (push)
git fetch origin
git checkout feature/py3
git pull
Already up to date.
# merge:
git checkout -b merge-master-to-py3-to-fix-ci-using-5726-$USER feature/py3
git merge origin/master
# To sign-off the merge commit:
git commit -s --amend
# Compare to pushed PR:
git remote add xenserver-next git@github.com:xenserver-next/xen-api.git
git fetch xenserver-next
git diff xenserver-next/merge-master-to-py3-to-fix-ocaml-ci-pr-5726
(no diff)
The latest master has another fix in the tests, it's worth dropping this merge and creating a new one
Pau wrote:
The latest master has another fix in the tests, it's worth dropping this merge and creating a new one
Edwin wrote:
might need to merge another CI fix from master
Thanks, because this PR now already has 4 approvals, I tend to like to merge it and open a new PR only for the remaining commits to be merged later.
In https://github.com/xapi-project/xen-api/pull/5731#issuecomment-2189273929, @psafont wrote:
That's great!
This PR is:
git merge master
intofeature/py3
.I repeated it a 2nd (and a 3rd) time and compared those to the PR/merge branch (see comments).
@stephenchengCloud
PS: Initially, I forgot to select feature/py3 in the GUI when opening the PR: Is corrected. The list of commits was always correct and GitHub is displaying the correct commits now. A reference PR in my test repo that shows the same commits is here: https://github.com/xenserver-next/xen-api/pull/25