#4792 PR from branch with %: 400 Bad Request
Opened 4 years ago by churchyard. Modified 4 years ago

I've accidentally named a branch %gochecks. Git seemed not to mind, so I went ahead.

I was able to push the branch to my fork:

$ git push -u churchyard %gochecks 
Enumerating objects: 15, done.
Counting objects: 100% (15/15), done.
Delta compression using up to 8 threads
Compressing objects: 100% (7/7), done.
Writing objects: 100% (8/8), 710 bytes | 355.00 KiB/s, done.
Total 8 (delta 4), 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 196 commits
remote: 
remote: Create a pull-request for %gochecks
remote:    https://pagure.io/fork/churchyard/packaging-committee/diff/master..%gochecks
remote: 
To ssh://pagure.io/forks/churchyard/packaging-committee.git
 * [new branch]      %gochecks -> %gochecks
Branch '%gochecks' set up to track remote branch '%gochecks' from 'churchyard'.

But the PR link there gives 400 Bad Request


Metadata Update from @pingou:
- Issue tagged with: bug

4 years ago

Login to comment on this ticket.

Metadata