Learn more about these different git repos.
Other Git URLs
Working on this PR [1], I tried to locally review the latest updates in the PR. To do that, I tried:
$ git fetch origin pull/19/head:pr_19 $ git checkout pr_19
But the checkout contained just the initial version of PR. At that moment, I thought I must be doing something wrong, so I opened the documentation [2] and update my .git/config with fetch = +refs/pull/*/head:refs/remotes/origin/pr/*, fetched the origin, checked out the pr/19 and again, the last commit on that branch is just the initial commit in the PR.
fetch = +refs/pull/*/head:refs/remotes/origin/pr/*
pr/19
There is something wrong. How am I supposed to get the latest commit, which was forced into the commit where the PR is taken from? I don't think this work properly.
Note the order of the fetch, the one for the +refs/pull/* must be above the one for +refs/heads/*. Then it should work
+refs/pull/*
+refs/heads/*
ping?
Metadata Update from @pingou: - Issue assigned to pingou
Hmm, testing this again, I get:
$ git fetch origin pull/19/head:pr_19 WARNING: 'ruby' is an alias for 'rpms/ruby' From ssh://pkgs.fedoraproject.org/ruby ! [rejected] refs/pull/19/head -> pr_19 (non-fast-forward)
which makes sense. $ git branch -D pr_19 and fetch again brings the latest commit.
$ git branch -D pr_19
Not sure if I changed something or something else changed since that time or if I was wrong (very likely) since the beginning. Please feel free to close the ticket for the moment and I'll be back if I have reproducer.
Thanks for the feedback, I can assure it also works for me, that's how I run the unit-tests on PR regularly.
Let's close for now and re-open if it happens again :)
Metadata Update from @pingou: - Issue close_status updated to: Invalid
Login to comment on this ticket.