Currently https://packagist.org/ is the main Composer repository. It aggregates public PHP packages installable with Composer.2 votes
Definitely on our roadmap!
I want to be able to login to myget and get a list of feeds i follow or favourite so if I need to setup my dev machine I have the public feeds ready, i dont have to search for them.2 votes
Good suggestion. It’s in our backlog.
It would be nice to be able to do client side building with the build services that would allow for grunt/gulp, npm/bower restores along with the traditional nuget restores. The output would be a folder of static artifacts and could also include .NET dll's. To expand this further ASP.NET 5 (vNext) comes with a KPM pack command. It would also be nice to allow for us to create nuget packages that are created from KPM pack commands.3 votes
We’re currently awaiting a RC for vNext so we can run builds of this type. Ideally, would you like us to run kpm pack? Or just make available kpm so you can run a build.bat which does npm, grunt and kpm pack in the end? Trying to figure out the most enjoyable workflow that makes it both generic enough for 90% of builds to always succeed by convention.
It appears that when someone adds a package to a proxied feed that I own, that it shows me as the person who added the package. Is it would be great if this was attributed to the actual user who originally caused the package to be added to the proxied feed.1 vote
Would it make sense to make this a MyGet system user instead? The reason is some users may not have permission to add packages to a feed and it would be confusing to see they actually added a package this way.
Right now, if I set a package retention rule up for a feed, once I exceed the max # of packages for that feed, there is an activity shown in the activity feed that makes it look like the owner account actively deleted the package. This has confused people and leads them to asking me why I am deleting packages.
Instead it would be nice if a system user was used and the act of a package being "pushed" out of the feed due to retention rules was not described in the same way as deleting a package manually.1 vote
- Don't see your idea?