-
Notifications
You must be signed in to change notification settings - Fork 243
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
Mark issues and pull requests as stale #6872
Mark issues and pull requests as stale #6872
Conversation
Signed-off-by: Ritu Deshmukh <[email protected]>
✅ Deploy Preview for odo-docusaurus-preview canceled.
|
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.
Added a few suggestions:
- Changed the number of days before marking an issue/PR as stale, and before closing it. Based on what I can see from old issues like this one, issues were marked as stale after 90 days of inactivity, and rotten/closed after an additional 30d of inactivity. I think this makes better sense.
- Leverage the
lifecycle/*
labels we already have: https://github.com/redhat-developer/odo/labels?q=lifecycle- This is useful in certain cases to exempt issues with certain labels from this action, for example, if they are explicitly labeled as active or frozen.
- More details in the stale message about when the issue will be closed
Co-authored-by: Armel Soro <[email protected]>
Co-authored-by: Armel Soro <[email protected]>
Co-authored-by: Armel Soro <[email protected]>
Co-authored-by: Armel Soro <[email protected]>
Co-authored-by: Armel Soro <[email protected]>
Co-authored-by: Armel Soro <[email protected]>
Co-authored-by: Armel Soro <[email protected]>
Kudos, SonarCloud Quality Gate passed! |
1 similar comment
Kudos, SonarCloud Quality Gate passed! |
Thank you for your reviews @rm3l .I have applied those changes as per your suggestions |
Reported in #6876 /override Kubernetes-Integration-Tests/Kubernetes-Docs-Integration-Tests |
@rm3l: Overrode contexts on behalf of rm3l: Kubernetes-Integration-Tests/Kubernetes-Docs-Integration-Tests In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Issues with attaching volumes on OpenShift. /override OpenShift-Integration-tests/OpenShift-Integration-tests |
@rm3l: Overrode contexts on behalf of rm3l: OpenShift-Integration-tests/OpenShift-Integration-tests In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What type of PR is this:
What does this PR do / why we need it:
Which issue(s) this PR fixes:
Fixes #6610
PR acceptance criteria:
Unit test
Integration test
Documentation
How to test changes / Special notes to the reviewer: