A build could succeed, including tests without generating any nuget packages. I should be nice to have a check in the build properties of each project which defined if a build should succeed when a nuget package is creator or not.10 votes
Hey X and M,
I like the product so far but the Add Package window definitely needs some improvement or a total makeover even. The autocomplete in the search bar is also flaky to scroll through.
Why not give the option to actually search and select from the resulting packages?1 vote
Bitbucket has a feature called "Deployment keys" which is primarily used for build services because they give read-only access to repositories, and does not count as an user license.
This would be great for small teams that uses bitbucket's free plan for 5 users, because we don's have to create a "fake" readonly user for myget's Build service.
I know that we can use our personal accounts as authentication, but I would rather not :-)16 votes
Build Service: it should be nice to be notified (email) when no build is trigger after a push operation.
Now you only get a notification if you start a manual within 5 minutes after the last build. I would like to get an email when this is happening after a git push operation3 votes
Situation: TeamCity build definitions with project names that contain capital letters. There are build templates that use the project name variable to do all sorts of things, from pulling from GitHub through to publishing packages.
MyGet forces all feed names to be lower-case, which means that we can't use project name variables to push to a MyGet feed.1 vote
It would be good to see what other packages in myget that has dependencies to the package currently being viewed.5 votes
Ability to create "Service" users who don't have an email address and aren't linked tro an identity provider
I would like to set up user accounts for our Build Servers that publish packages and our Octopus Deploy server that needs read only access to our Package Feeds.
Currently I can't set this up as the users in question are obviously not people and don't have email addresses for them.8 votes
We are thinking of making API keys “scoped”, so that you can create an API key that, for example, can only consome and/or push to a given feed. Would that work?
The scenario goes like this: An enterprise wants to have private feeds, that only customers that paid for a package can access them. Different customers need to have different credentials.
i've seen that myget enterprise only has "developer" users.
is there something already implemented that helpes to this scenario?
Clients may be hundreds for a team of 10 developers.
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.
Would be awesome to have some mobile integration, so that I can get a push notification when a new packages has been built, click the notification and be taken to a MyGet mobile app, that allows me to publish to nuget.org with one more click.
Maybe a mobile version of the site would be enough?6 votes
It would be nice to get a progress indication when uploading packages (especially for larger ones).11 votes
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 if packages that were completely unlisted where shaded red or something to indicate that status without having to click through.2 votes
- Don't see your idea?