Create Pull Request Button is disabled
Asked Answered
S

11

71

I would like to make a pull request from my fork repo to the upstream repository.

As always I was following these steps here from the guidance from Github.

But this time I can not make a pull request, as the button is disabled.

The branches can be automatically merged.

I do have changes in my forked repo and I can see commits made. Base repo and head repo are indicated correctly.

Servo answered 10/4, 2019 at 7:17 Comment(6)
What happens after you've filled in the title and description? Are there enabled options in the dropdown on that button?Deflexed
Hi, welcome to SO. While a screenshot can sometimes be useful, this one is maybe not showing the most informative things for the problem at hand. You said the button was disabled and we're ready to take your word for it, no need for a proof. What would be more useful is your branches situation.Metcalf
Well, title is filled in as well as the description, but still, the button is disabled. @Deflexed Do you mean the "create draft pull request" option from dropdown? If yes, it is disabled alsoServo
@RomainValeri you are right, the image is unnecessary. What about branches situation?Servo
Are the branches to be merged from different repos? Have you double-checked authorizations for submitting pull requests here?Metcalf
happened to me before and it was because i forgot to add titleAludel
S
8

From Github Developer Support:

Also, I know this might seem strange, but could you try selecting the base repo/branch from the drop down list (even if this already seems selected), and give this another go. It could that, for whatever reason, the pull request creation flow isn't picking this up implicitly.

I have also logged out and logged in again.

After that, everything was fine!

Servo answered 11/4, 2019 at 13:10 Comment(0)
S
190

In my case, the pull request Title field didn't auto-populate like it usually does. Once I typed in a title, the button became active.

Salba answered 19/11, 2019 at 7:35 Comment(4)
This happened to me when making changes related to the readmeIngalls
An indicator wouldn't hurt.Rochkind
Was my issue as well, thanks for posting this "obvious" answer, saved me some time.Jaclynjaco
lol, it happened to me as well :)Bael
B
12

make sure to put something in the title, I forgot to add one here enter image description here

Baobaobab answered 21/7, 2022 at 14:39 Comment(0)
S
8

From Github Developer Support:

Also, I know this might seem strange, but could you try selecting the base repo/branch from the drop down list (even if this already seems selected), and give this another go. It could that, for whatever reason, the pull request creation flow isn't picking this up implicitly.

I have also logged out and logged in again.

After that, everything was fine!

Servo answered 11/4, 2019 at 13:10 Comment(0)
R
2

I couldn't see a button at all... and then I realised...

I wasn't logged in #facepalm

Retroactive answered 3/1, 2022 at 1:33 Comment(0)
A
2

Hello I encountered the same issue then noticed that the button is inactive because you have not given the title to the PR. Make sure you give the PR title.

Adne answered 6/4, 2023 at 15:46 Comment(1)
Please don't repeat answersReputed
Q
1

Populating the "comment" field did it for me.

Quadrillion answered 22/9, 2020 at 14:11 Comment(0)
O
0

It happened to but I realized that and immediately changed the default branch to master. The pull request button got activated thereoff.

Oppen answered 24/7, 2020 at 10:15 Comment(0)
A
0

After realising it's just a HTML issue, I enabled the button by inspecting the element and deleting the tag in my browser (Safari).

That should fix the issue in other browsers too.

Acrilan answered 1/3, 2021 at 23:40 Comment(0)
M
0

I had to select my branch from the list shown down on the github page labeled "There isn’t anything to compare." - weird but worked fine.

Macon answered 20/8, 2021 at 20:54 Comment(0)
J
-1

I had the same issue. Adding a title to pr fixed the problem

Junji answered 29/4, 2022 at 11:13 Comment(1)
This is the same solution as in this other answer.Kelter
A
-1

None of the answers here worked for me - I was able to resolve it by switching from chrome to firefox.

Appoggiatura answered 3/4 at 2:33 Comment(0)

© 2022 - 2024 — McMap. All rights reserved.