Skip to content

Conversation

@artidoro
Copy link
Contributor

@artidoro artidoro commented Sep 6, 2018

Fixes #483.

I based my change on the old version of the file which pushed to the VSTS feed only. In order to keep pushing to MyGet and also push to VSTS I added a new task to the yaml file. The task is identical to what was found in the old version of the file.

However, I don't know how to test this code and make sure that it works.

@artidoro artidoro force-pushed the VSTS branch 2 times, most recently from 16ea450 to ba3406b Compare September 6, 2018 06:06
Copy link
Member

@eerhardt eerhardt left a comment

Choose a reason for hiding this comment

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

Thanks for taking care of this, @artidoro.

@artidoro
Copy link
Contributor Author

artidoro commented Sep 6, 2018

Check:
After manually pushing to VSTS and building, the packages are published to the VSTS's artifacts tab.

Copy link
Contributor

@Ivanidzo4ka Ivanidzo4ka left a comment

Choose a reason for hiding this comment

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

:shipit:

@eerhardt eerhardt merged commit a6e3c0a into dotnet:master Sep 10, 2018
@artidoro artidoro deleted the VSTS branch January 5, 2019 00:02
@ghost ghost locked as resolved and limited conversation to collaborators Mar 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants