| |
@@ -118,12 +118,12 @@
|
| |
|
| |
fetch = +refs/pull/*/head:refs/remotes/origin/pr/*
|
| |
|
| |
- to that section, like this::
|
| |
+ to that section as **the first fetch line**, like this::
|
| |
|
| |
[remote "origin"]
|
| |
url = ssh://git@pagure.io/pagure.git
|
| |
- fetch = +refs/heads/*:refs/remotes/origin/*
|
| |
fetch = +refs/pull/*/head:refs/remotes/origin/pr/*
|
| |
+ fetch = +refs/heads/*:refs/remotes/origin/*
|
| |
|
| |
Obviously, the remote url should be matching the url of your project (pagure project in
|
| |
this example).
|
| |
If the PR fetch line is not stated as the second one in git config, then
the branch is configured with a standard merge remote, and the PR branch
can't be pulled. The specific PR fetch line has to be stated as the
first one.
WARNING: I have no idea what I'm doing. Somebody with proper git knowledge needs to check this is sane!
Today I found out that if I configure my pagure checkout according to the documentation, I can check out
pr/NN
branch, but I can't pull changes. Example:This is how
.git/config
looks like:And if I switch the order of those
fetch
lines:And
.git/config
: