-
Notifications
You must be signed in to change notification settings - Fork 258
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
Missing announcements for three new specs #5924
Comments
All of these specs will be announced when they are ready to be reviewed. Right now these are in incubated state which means we are still adding details. I guess the first one is close to be announced. |
Thanks! BTW do check permissions for https://github.com/NuGet/Announcements/issues - seems everyone could in theory announce things there. |
It seems its not possible to limit issue creation to some, on a public GitHub repo. https://help.github.com/articles/creating-an-issue/ I see the same is the case for https://github.com/dotnet/announcements repo. Is there an alternative way to achieve this? |
Indeed! Just tried on one of my own repo's, issues always seem possible. Ah well, guess it's clear in that repo others should not be posting. Thanks @anangaur for checking! |
Feel free to close this issue or wait for the above specs do be announced and then close :) |
Closing for now. |
In case anyone missed these (they were announced overnight in various issues/comments but not (yet?) part of the NuGet/Announcements) repo:
@karann-msft / @anangaur Seems anyone can post to https://github.com/NuGet/Announcements/issues, is that intended? (may want to set that to project admins only)
The text was updated successfully, but these errors were encountered: