I am trying to upload a package for modders on my repository (console application) and I have set up nuget.exe using the GitHub Package Registry configuration for NuGet steps on Help.
When I tried to push my .nupkg file to GitHub, using nuget.exe, I got an error after uploading, saying 400 Bad Request.
I have set the API key to the source, because I think it is a root cause, but when I tried to upload it with new changes, the same 400 Bad Request error appears.
I used nuget push KS.0.0.6.13.symbols.nupkg -Source "GitHub - KS" for uploading to GitHub NuGet repo. I have set the site as "https://nuget.pkg.github.com/EoflaOE/index.json" and username as "EoflaOE".
My repository is .NET Framework 4.7.x console application, and is found at "https://github.com/EoflaOE/Kernel-Simulator", for future reference. It is a kernel simulator that can be an API for making modifications that compile and run inside an app.
Did you ever resole or figure this out @EoflaOE ?
As I have the same issue with my package by trying to use the new GitHub Actions CI YML Workflows
@warrenbuckley Did you get the notification saying that you're accepted? I didn't.
I contacted them and they said that I am on the list but not accepted yet.
Hmm I am pretty sure I got an email to say I was accepted for this.
I have a support ticket I am waiting to hear back from on how to use this in GitHub Actions, but they have not told me that I am NOT in the BETA, so I assume I am.
Still, I did not get an email. Can you please tell them to add me to the beta? If you do, I will let you be a member of my project.
Just raised a support ticket for similar NuGet problems - I get "invalid response" from GH Package Repo every time I try to push, but NuGet works fine so I know the package is okay. On package repo and actions beta so I'll let you know if I hear anything
@stoiveyp Thanks! The problem on my end is that GitHub didn't accept my beta request, and I have to wait for months. What can I do to let them speed up?