Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix incorrect MyGet push URL #1031

Closed
CharliePoole opened this issue Nov 8, 2021 · 2 comments · Fixed by #1032
Closed

Fix incorrect MyGet push URL #1031

CharliePoole opened this issue Nov 8, 2021 · 2 comments · Fixed by #1032
Assignees
Milestone

Comments

@CharliePoole
Copy link
Contributor

CharliePoole commented Nov 8, 2021

The last two merges failed to push the artifacts to MyGet because of an incorrect push URL. We should continue to push to https://www.myget.org/F/nunit/api/v2

NOTE: MyGet.org says to use https://www.myget.org/F/nunit/api/v2/package, but for now I'm just going to change it back to the URL we were using before the failure.

The changes from those two failed pushes are already in master, so fixing this should bring the latest myget dev release up to date.

@CharliePoole CharliePoole added this to the 3.13 milestone Nov 8, 2021
@CharliePoole CharliePoole self-assigned this Nov 8, 2021
@CharliePoole
Copy link
Contributor Author

An observation...

This was a bit confusing, because I had made the change to the URL back in May. It was one of those kinds of build changes, which can only be verified after the code is merged, and it was only merged a few days ago. That's when any subsequent merges could no longer complete.

Maybe those types of merges need to be done separately from any code changes and merged as quickly as possible. In some projects, I make those kinds of changes directly on master but the operating rules of this project don't allow that.

@CharliePoole
Copy link
Contributor Author

This change merged and the MyGet 3.13.0-dev-05337 build now has all the changes previously merged into master. Only two merges were missed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant