-
Notifications
You must be signed in to change notification settings - Fork 63
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
add needs-triage workflow #1199
Conversation
Signed-off-by: Stephanie <[email protected]>
Signed-off-by: Stephanie <[email protected]>
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.
LGTM assuming no issues with using label
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: amisevsk, johnmcollier, yangcao77 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
New changes are detected. LGTM label has been removed. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1199 +/- ##
=======================================
Coverage 35.75% 35.75%
=======================================
Files 52 52
Lines 6696 6696
=======================================
Hits 2394 2394
Misses 4158 4158
Partials 144 144 ☔ View full report in Codecov by Sentry. |
@yangcao77 We are no longer using the |
This PR is stale because it has been open for 90 days with no activity. Remove stale label or comment or this will be closed in 60 days. |
What does this PR do?
This PR adds a workflow to always add needs-triage label to new/reopen issues.
copied over from odo's repo: https://github.com/redhat-developer/odo/blob/bc168518d169f2975040ba29dae2b334ebfddbb5/.github/workflows/issue-management.yaml#L17C1-L31C48
Which issue(s) does this PR fix
a to-do thing to adopt the new team operation process: https://docs.google.com/document/d/1IkujxkkrqdnXjmITGAIOCdAb4kH_ql_KexlWSpc8vEA/edit#heading=h.57d81ski9zgr
PR acceptance criteria
Testing and documentation do not need to be complete in order for this PR to be approved. We just need to ensure tracking issues are opened.
Unit/Functional tests
QE Integration test
Documentation
Client Impact
How to test changes / Special notes to the reviewer