- Notifications
You must be signed in to change notification settings - Fork714
Add github actions for issue health#7007
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:main
Are you sure you want to change the base?
Uh oh!
There was an error while loading.Please reload this page.
Conversation
dibarbet left a comment• edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Seems reasonable!
| with: | ||
| github-token: ${{secrets.GITHUB_TOKEN}} | ||
| script: | | ||
| const labelName = 'needs-more-info'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
we have two needs more info labels. Fine with using this one, but we should transition issues under the old one to it and delete the old one
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
All our new labels seem to be of the space format. Do we want to keep that and delete the hyphenated version? The hyphenated has 0 issues under it anyway
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Fine with either. easiest is probably just to use the one with spaces since we on't have to move labels
| "Project System": "@jasonmalinowski", | ||
| "Question": "@mikadumont", | ||
| "Razor": "@phil-allen-msft", | ||
| "Unity": "@jbevain" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
At some point it might be useful to create (or re-use) a few different github groups here. For example we could have a debugger set, razor set, unity set, etc. Then we can live update the groups without needing to modify this.
Totally fine with this as v1 though.
No description provided.