-
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
bucket for major pack related issues #6285
Labels
Epic
Functionality:Pack
Priority:2
Issues for the current backlog.
Type:Tracking
This issue is tracking the completion of other related issues.
Comments
39 tasks
Please include this too: #6317 |
rohit21agrawal
added
the
Priority:1
High priority issues that must be resolved in the current sprint.
label
Jun 6, 2018
Issue to be considered: #8827 We should have corefx folks depend on our task instead of wiring up their own. |
I'm gonna probably use this as a new Epic to track stuff needed for Pack |
@zkat Is this epic still p1? |
zkat
added
Priority:2
Issues for the current backlog.
and removed
Priority:1
High priority issues that must be resolved in the current sprint.
labels
Aug 25, 2021
Nope :) |
@zkat it's not in any sprints, is there a reason for this? |
Issue is missing Type label, remember to add a Type label |
nkolev92
added
Type:Tracking
This issue is tracking the completion of other related issues.
and removed
missing-required-type
The required type label is missing.
labels
Sep 5, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Epic
Functionality:Pack
Priority:2
Issues for the current backlog.
Type:Tracking
This issue is tracking the completion of other related issues.
The listed issues are important customer asks and each of them have been receiving considerable feedback , we should definitely look into getting them fixed as soon as we can as this will also help us in asking the ecosystem to move the PackageReference from packages.config
dotnet nuget push *.nupkg
doesn't push more than one file #4393The text was updated successfully, but these errors were encountered: