#9578 Renamig some branches to main leaves master in the message from remote
Closed: Upstream by kevin. Opened by churchyard.

I've just pushed to my fork of fedora-kickstarts and I got:

$ git push -u churchyard classroom-no-inkscape 
Enumerating objects: 20, done.
Counting objects: 100% (20/20), done.
Delta compression using up to 8 threads
Compressing objects: 100% (15/15), done.
Writing objects: 100% (15/15), 2.05 KiB | 2.05 MiB/s, done.
Total 15 (delta 9), reused 0 (delta 0), pack-reused 0
remote: Has commit access: True
remote: Has commit access: True
remote: Sending to redis to send commit notification emails
remote: * Publishing information for 545 commits
remote: 
remote: Create a pull-request for classroom-no-inkscape
remote:    https://pagure.io/fork/churchyard/fedora-kickstarts/diff/master..classroom-no-inkscape
remote: 
To ssh://pagure.io/forks/churchyard/fedora-kickstarts.git
 * [new branch]      classroom-no-inkscape -> classroom-no-inkscape
Branch 'classroom-no-inkscape' set up to track remote branch 'classroom-no-inkscape' from 'churchyard'.

https://pagure.io/fork/churchyard/fedora-kickstarts/diff/master..classroom-no-inkscape gives error 400, bad request.

It should be https://pagure.io/fork/churchyard/fedora-kickstarts/diff/main..classroom-no-inkscape


This is an upstream pagure issue and better reported on pagure.io/pagure.

That said, the underlying issue is that it uses the default branch from the fork (which is still master for your fork).

I'll see upstream if we can improve that.

Filed https://pagure.io/pagure/issue/5086 for it.

Metadata Update from @kevin:
- Issue close_status updated to: Upstream
- Issue status updated to: Closed (was: Open)

Thanks @kevin

Metadata