-
Notifications
You must be signed in to change notification settings - Fork 13
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
Prescription build is failing adviser release #2402
Labels
kind/bug
Categorizes issue or PR as related to a bug.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
sig/stack-guidance
Categorizes an issue or PR as relevant to SIG Stack Guidance.
Comments
/sig stack-guidance |
sesheta
added
sig/stack-guidance
Categorizes an issue or PR as relevant to SIG Stack Guidance.
kind/bug
Categorizes issue or PR as related to a bug.
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
labels
Jan 9, 2023
codificat
added
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
and removed
priority/critical-urgent
Highest priority. Must be actively worked on as someone's top priority right now.
labels
Jan 9, 2023
/assign |
Should we delete invalid prescriptions completely ? With the pre-commit hooks working it should be quite easy to get a list of offending files. |
/assign |
/unassign |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/bug
Categorizes issue or PR as related to a bug.
priority/important-soon
Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
sig/stack-guidance
Categorizes an issue or PR as relevant to SIG Stack Guidance.
Prescription build is failing adviser release.
Logs:
Originally posted by @harshad16 in #2401 (comment)
Acceptance criteria
re-enable the ones that are not affected? NoRelated work:
The text was updated successfully, but these errors were encountered: