GitHub Community
Passing long body to issues/new?title=body= #22946
-
|
RE: About automation for issues and pull requests with query parameters Hi I am looking at utilizing info from this page to build a custom issue creation feature for my users. Basically when an error occurs, users can click a “Report an error” button which will redirect users to the github issue creation page with “body” prefilled with tracebacks and debug logs, etc. Depending on the nature of error, body can be quite lengthy when raw debug outputs are attached which currently results in a 414 Request-URI Too Large error. Is there anyway for me to pass a long body into the the issues endpoint (maybe a POST request?), I imagine long body in Github Issues is something that can be anticipated. Really appreciate any help and ideas : P ! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
This post was moved to a different board that fits your topic of discussion a bit better. This means you’ll get better engagement on your post, and it keeps our Community organized so users can more easily find information. As you’ll notice, your Topic is now in the How to use Git and GitHub board. No action is needed on your part; you can continue the conversation as normal here. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @wei, Thanks for being part of the Community Forum! There’s no direct workaround for using URL parameters that are too long. However, if you can provide more details about your specific workflow and goals, you might be able to use an alternative. Specifically, if you need to include specific browser info, it may be easier for you to create a POST request to the API to create an issue and offer the user directions on adding additional information in a comment. Of course, if your workflow relies on author data for anything, that may not be the best solution. On the other hand, if youre not grabbing in-the-moment data, you could use an issue template instead of the URL parameters. One other option: If all you’re collecting is browser info, you could workaround the URL parameter issue by using a service like a whatsmybrowser.org URL, instead of including all the specific info in the URL. I hope this helps! |
Beta Was this translation helpful? Give feedback.
Hi @wei,
Thanks for being part of the Community Forum!
There’s no direct workaround for using URL parameters that are too long. However, if you can provide more details about your specific workflow and goals, you might be able to use an alternative.
Specifically, if you need to include specific browser info, it may be easier for you to create a POST request to the API to create an issue and offer the user directions on adding additional information in a comment. Of course, if your workflow relies on author data for anything, that may not be the best solution.
On the other hand, if youre not grabbing in-the-moment data, you could use an issue template instead of the URL parameters.
One oth…