-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
fix: Remove duplicated stale job #6416
fix: Remove duplicated stale job #6416
Conversation
Signed-off-by: Mateus Oliveira <msouzaol@redhat.com>
.github/workflows/stale-issues.yml
Outdated
@@ -13,12 +12,15 @@ jobs: | |||
repo-token: ${{ secrets.GITHUB_TOKEN }} | |||
stale-issue-message: "This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. If a Velero team member has requested log or more information, please provide the output of the shared commands." | |||
close-issue-message: "This issue was closed because it has been stalled for 5 days with no activity." | |||
days-before-issue-stale: 30 | |||
days-before-issue-close: 5 | |||
days-before-issue-stale: 30 # 60 |
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 keep the days of the other job?
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.
My opinion is to use the longer setting.
.github/workflows/stale-issues.yml
Outdated
# Disable stale PRs for now; they can remain open. | ||
days-before-pr-stale: -1 | ||
days-before-pr-close: -1 | ||
# Only issues made after Feb 09 2021. | ||
start-date: "2021-09-02T00:00:00" | ||
# Only make issues stale if they have these labels. Comma separated. | ||
only-labels: "Needs info,Duplicate" | ||
# only-labels: "Needs info,Duplicate" |
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.
Only labels work like a "AND", not a "OR", so only issues that have both these labels would be marked as staled. More info
I think keeping what the old job was doing with exempt-issue-labels
is good
days-before-issue-close: 5 | ||
days-before-issue-stale: 30 # 60 | ||
days-before-issue-close: 5 # 14 | ||
stale-issue-label: staled | ||
# Disable stale PRs for now; they can remain open. | ||
days-before-pr-stale: -1 |
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.
I like the idea of just marking issues as staled, but not PRs
Codecov Report
@@ Coverage Diff @@
## main #6416 +/- ##
==========================================
+ Coverage 53.77% 53.81% +0.03%
==========================================
Files 228 228
Lines 23777 23777
==========================================
+ Hits 12787 12795 +8
+ Misses 10043 10036 -7
+ Partials 947 946 -1 |
Signed-off-by: Mateus Oliveira <msouzaol@redhat.com>
Signed-off-by: Mateus Oliveira <msouzaol@redhat.com>
Thank you for contributing to Velero!
Please add a summary of your change
Remove duplicated stale job from project.
Does your change fix a particular issue?
Fixes #6386
Please indicate you've done the following:
/kind changelog-not-required
as a comment on this pull request.site/content/docs/main
.