Skip to content
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

Merged
merged 3 commits into from
Jun 30, 2023

Conversation

mateusoliveira43
Copy link
Contributor

@mateusoliveira43 mateusoliveira43 commented Jun 21, 2023

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:

  • Accepted the DCO. Commits without the DCO will delay acceptance.
  • Created a changelog file or added /kind changelog-not-required as a comment on this pull request.
  • Updated the corresponding documentation in site/content/docs/main.

Signed-off-by: Mateus Oliveira <msouzaol@redhat.com>
@@ -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
Copy link
Contributor Author

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?

Copy link
Contributor

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.

# 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"
Copy link
Contributor Author

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
Copy link
Contributor Author

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

@blackpiglet blackpiglet added the kind/changelog-not-required PR does not require a user changelog. Often for docs, website, or build changes label Jun 22, 2023
@codecov-commenter
Copy link

Codecov Report

Merging #6416 (58bfd3e) into main (ef443fe) will increase coverage by 0.03%.
The diff coverage is n/a.

@@            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     

see 1 file with indirect coverage changes

Signed-off-by: Mateus Oliveira <msouzaol@redhat.com>
blackpiglet
blackpiglet previously approved these changes Jun 27, 2023
Signed-off-by: Mateus Oliveira <msouzaol@redhat.com>
@sseago sseago merged commit dcdd5f9 into vmware-tanzu:main Jun 30, 2023
22 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/changelog-not-required PR does not require a user changelog. Often for docs, website, or build changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[DEVELOPMENT] Duplicated stale job
4 participants