Skip to content

Conversation

@gregg-miskelly
Copy link
Contributor

When we released the extension, I forgot to remove the myget feed from our NuGet.config,
I was assuming this wouldn't really matter since nuget.org came first in the list, by
the myget folks reported a traffic spike, so I am assuming we should really remove this.

@gregg-miskelly
Copy link
Contributor Author

We are waiting on a response from the myget.org team to understand the priority of this to understand if we should fix it now, or just before we release the next time.

<clear />
<add key="api.nuget.org" value="https://api.nuget.org/v3/index.json" />
<!-- This dependency can be commented out once we push packages to nuget for a real release -->
<add key="coreclrdebug" value="https://www.myget.org/F/coreclr-debug/api/v3/index.json" />
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we want to comment this out instead of delete it? Are we still planning on pushing daily builds to myget?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are still going to push daily builds to myget, but my hope is that I can get git to leave this commit in the master branch by manually resolving the conflict if we merge back to master.

When we released the extension, I forgot to remove the myget feed from our NuGet.config,
I was assuming this wouldn't really matter since nuget.org came first in the list, by
the myget folks reported a traffic spike, so I am assuming we should really remove this.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants