General
Welcome to MyGet’s UserVoice forum! We encourage you to leave some feedback about missing features, stuff you wish for us to include in MyGet, …
-
Make feed names in URLs case-insensitive.
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 -
Make it possible to view packages that depend on a specific package
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 votesWe 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?
-
5 votes
-
Enterprise client management for payed packages
hello
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.thanks
3 votes -
Attribute adding of packages to a proxy feed to user who triggers the add, not the owner
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 voteWould 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.
-
7 votes
-
Provide mobile apps to publish packages
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 -
Show package upload progress indication
It would be nice to get a progress indication when uploading packages (especially for larger ones).
11 votes -
Option to favourite/follow a feed
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 votesGood suggestion. It’s in our backlog.
-
Display unlisted packages grayed out
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 -
Feed endpoints clarification
I spent a while trying to fix what appeared to be a broken upload of symbols to myget. I am new to myget.
I misread the Feed Details page because the v3 and v2 endpoints are all listed in the same block and only the v2 one has a push URL.
I thought this meant that the first 4 endpoints were just for fetching packages for v3 and v2 and the 5th one ("Push Nuget packages To") was therefore for both v2 and v3.
A really small change would be to clarify with the titles that V3 uses the same…
0 votes
- Don't see your idea?