-
-
Notifications
You must be signed in to change notification settings - Fork 231
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow addins to be marked as pre-release or beta #184
Comments
We can currently mark addins as prerelease in the YAML data for the purpose of downloading the NuGet package. Is this issue about bringing that indication forward to the GUI? |
@daveaglick that's a good point displaying that it's prerelease under addins makes sense, As we now have the info. Perhaps under addins we even could suggest #addin nuget:?package={addin}&prerelease or for non preview #addin nuget:?package={addin} Just as nuget.org suggests
or for non preview
|
augustoproiete
added a commit
to augustoproiete-forks/cake-build--website
that referenced
this issue
Nov 29, 2020
…rocessor directive
2 tasks
augustoproiete
added a commit
to augustoproiete-forks/cake-build--website
that referenced
this issue
Nov 29, 2020
…rocessor directive
pascalberger
added a commit
that referenced
this issue
Nov 29, 2020
…-pre-release (GH-184) Display info when add-in is pre-release & fix preprocessor directive
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As discussed with @gep13 in this issue in one of my repositories, it would be nice if add-ins could be listed but marked as pre-release on the site. My use case is that I have an add-in that definitely falls in the "works on my machine" status. It invokes MAGE.exe for building click-once apps and frankly I'm kind of annoyed we still use click-once so I'm not really going to be spending a ton of time testing every scenario out on it on the weekends.
But it should work. I think others would find value in it, and maybe someone that really loves click-once could test contribute to get it to a 1.0 stage. And the best place for me to get the word out would be the add-in list, but I'd like to set expectations on its current state.
The text was updated successfully, but these errors were encountered: