Same Jenkins issue as my previous PR (#570) — Jenkins is looking for my branch in the wrong repo.

+ git clone https://pagure.io/fedpkg.git -b master
Cloning into 'fedpkg'...
+ cd fedpkg
++ git remote
+ remotes=origin
+ echo origin
+ grep -q '^proposed$'
+ git remote add proposed https://pagure.io/fedpkg.git
+ git fetch proposed
From https://pagure.io/fedpkg
 * [new branch]      master     -> proposed/master
+ git checkout origin/master
Note: switching to 'origin/master'.
[...]
+ git merge --no-ff proposed/dependencies -m 'Merge PR'
merge: proposed/dependencies - not something we can merge

The Jenkins parameters are apparently not set correctly for "Remote PRs":

https://jenkins-fedora-infra.apps.ocp.cloud.ci.centos.org/job/fedpkg-pipeline/294/parameters/

(Note "REPO" being incorrectly set to https://pagure.io/fedpkg.git instead of https://pagure.io/forks/ferdnyc/fedpkg.git.)

Commit 0939d876 fixes this pull-request

Thanks for the change,
I couldn't normally rebase the PR, so I merged it manually. But right after the merge, tests were passing:
https://jenkins-fedora-infra.apps.ocp.cloud.ci.centos.org/job/fedpkg-pipeline/335/

@onosek I'm telling you, I can't wait for the new forge.