Error 500 when creating a pull request.

[nicolasay1]

Select Topic Area

Bug

Body

Hi,

I am working on a project and pushed code on a branch to create a pull request. When clicking on the Create Pull Request button, I get redirected to a Error 500 page, and cannot create the pull request.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[tvillafane]

I'm also getting 500s when I try to add a comment to an existing PR.

[eric-ba]

also getting errors opening PRs

[zavvdev]

Same for me. Can't create new PR

[mngatewood]

I am having the same issue as the OP. Tried multiple browsers with the same result.

[festelle]

I'm having the same issue when trying to create a PR.

[LucaACM]

same as this boy, but worst

[kazza7ambientes]

Would you like me to explain common PR-related errors and possible fixes?

[Darrilla]

404 errors for me. Also, try viewing files changed for any existing PR. 404

[Darrilla]

Correction - it was a 404, now it is a 500

[rodrigoinco]

I'm having the same issue!

[ryan-case-ml]

Also having issues viewing files changed on a PR. Getting a 500 page

[jilladams]

Also getting an error when trying to comment on Issues:

Failed to fetch data. Please use this request ID when contacting support: F44E:2885B2:1DDE766:1E657B3:674F60A5 Error: undefined: Something went wrong while executing your query. Please include `F44E:2885B2:1DDE766:1E657B3:674F60A5` when reporting this issue. (path: undefined)
(anonymous) @ fetch-graphql.ts:118
(anonymous) @ fetch-graphql.ts:116
m @ fetch-graphql.ts:73
await in m
f @ fetch-graphql.ts:144
(anonymous) @ relay-environment.ts:120
(anonymous) @ relay-environment.ts:122
(anonymous) @ RelayObservable.js:350
t.subscribe @ RelayObservable.js:363
(anonymous) @ RelayObservable.js:86
(anonymous) @ RelayObservable.js:350
t.subscribe @ RelayObservable.js:363
e @ OperationExecutor.js:90
execute @ OperationExecutor.js:31
(anonymous) @ RelayModernEnvironment.js:278
(anonymous) @ RelayObservable.js:350
t.subscribe @ RelayObservable.js:363
e.exports @ commitMutation.js:56
i @ add-comment-mutation.ts:29
(anonymous) @ IssueCommentComposer.tsx:162
onSave @ IssueCommentComposer.tsx:343
(anonymous) @ CommentBox.tsx:171
eO @ react-dom.production.min.js:54
ej @ react-dom.production.min.js:54
(anonymous) @ react-dom.production.min.js:55
n7 @ react-dom.production.min.js:55
re @ react-dom.production.min.js:106
(anonymous) @ react-dom.production.min.js:117
u_ @ react-dom.production.min.js:273
eL @ react-dom.production.min.js:52
ro @ react-dom.production.min.js:109
tO @ react-dom.production.min.js:74
tI @ react-dom.production.min.js:73

[cristi11191]

I have the same problem
but I got this

[cristi11191]

Let's wait until tomorrow, I think they're sleeping !

[satishkura-se]

we are also having similar issue

[cebrix]

We are doomed!

[clayton-duarte]

same problem on my PRs 😢

[Kallenhard1]

Here too!

[MaxwellDAssistek]

Also when trying to create an issue!

[Suedagostino]

I am also getting a 500 when creating a pull request

[Suedagostino]

appears to be fixed now

[et3rnalvoid]

Also getting error 500 when opening an issue

[techy4shri]

If you're experiencing a 500 Internal Server Error it's likely an issue on GitHub's end.
Which currently, it is. The current staus can be checked here (https://www.githubstatus.com/)

The same can be seen on the support page too: (https://support.github.com)

Sometimes, server errors are temporary and can be resolved by waiting for a while and then refreshing the page. For the future, you can also check GitHub's status page (https://www.githubstatus.com/) to see if there are any ongoing incidents or outages reported.

If the issue persists, or in case the status is updated as fine and you still experience this issue, you can also consider reaching out to the guys at GitHub Support.

Now I hope this helped :)

[webdevbynight]

I have been having the same problem for a few minutes, despite the incident being marked as resolved.

[jtw-r]

I believe this is a regression. It was fixed a few hours ago and I was able to open/close PRs. I think this is a new issue.

Still sucks :(

[rassakhatsky]

Same issue, it's clearly not resolved.

[youngang]

Same - a coworker and I are still having this issue

[mfioretti-sm]

Still getting 500 Error, despite marked as resolved

[soundasleep]

It is still very broken here in New Zealand too.

[cwagrant]

You say there's no active incidents but I would say this is a rather large incident and it's still active as people still can't create pull requests.

[clintont]

There is still an issue in California, USA

[pamelagilmour]

I ran into the same issue but it now seems to be resolved as I was able to make a PR successfully. In California.

[webdevbynight]

Same for me. In France.

[soundasleep]

Working again!

[mfioretti-sm]

worked here in Canada just now

[ghostinhershell]

Hey guys, thanks so much for reaching out in our community! It looks like there was an incident reported on our Status page yesterday that affected both Pull Requests and API Requests: https://www.githubstatus.com/incidents/w6g0cmvyx3vm. This issue was resolved, shortly after it first appeared, yesterday at 20:05 UTC.

For future reference, you can check our GitHub Status Page to see for real-time and historical data on system performance + subscribe to issues for updates.

Cheers!

[Darrilla]

It was a good 15 minutes at least before the status page showed anything wrong