Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

chore: add a stale workflow#1789

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

Merged
nejch merged 1 commit intomainfromjlvillal/stale
Jan 7, 2022
Merged

chore: add a stale workflow#1789

nejch merged 1 commit intomainfromjlvillal/stale
Jan 7, 2022

Conversation

JohnVillalovos
Copy link
Member

@JohnVillalovosJohnVillalovos commentedDec 31, 2021
edited
Loading

Use the stale action to close issues and pull-requests with no
activity.

Issues: It will mark them as stale after 60 days and then close
them once they have been stale for 15 days.

Pull-Requests: It will mark pull-requests as stale after 90 days and then close
them once they have been stale for 15 days.

https://github.com/actions/stale

Closes:#1649

nejch and max-wittig reacted with thumbs up emoji
@nejch
Copy link
Member

I like this a lot! I'm still thinking about my comment from#1649 (comment). I'd limit it to issues and PRs where we're getting stuck because of user inaction, with no clarification - and not those that are confirmed bugs/valid requests but we haven't done anything about them. Does that make sense?

For that we could maybe useonly-* orexempt-* with some of our existing labels, or think of something new. We do useawaiting feedback quite a lot, that would be a good candidate for example.

I'd also make it a bit more lenient (maybe 90 days for stale, 15 days to close) in case people are on vacation? Sometimes even I don't respond to an issue within 30 days.. 😸

@JohnVillalovos
Copy link
MemberAuthor

I like this a lot! I'm still thinking about my comment from#1649 (comment). I'd limit it to issues and PRs where we're getting stuck because of user inaction, with no clarification - and not those that are confirmed bugs/valid requests but we haven't done anything about them. Does that make sense?

For that we could maybe useonly-* orexempt-* with some of our existing labels, or think of something new. We do useawaiting feedback quite a lot, that would be a good candidate for example.

That could work. Just need to figure out what we want to use. But I would useexempt-* as want this automated not something where we need to tag something before it will get automatically moved to stale.

I'd also make it a bit more lenient (maybe 90 days for stale, 15 days to close) in case people are on vacation? Sometimes even I don't respond to an issue within 30 days.. 😸

90 days! Seems so long 😁 But yeah can do that.

@JohnVillalovosJohnVillalovosforce-pushed thejlvillal/stale branch 4 times, most recently from43f1743 to0b87e22CompareJanuary 4, 2022 05:49
Copy link
Member

@nejchnejch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

I think we can go ahead with this with a few labels as suggested above@JohnVillalovos WDYT?

Use the stale action to close issues and pull-requests with noactivity.Issues: It will mark them as stale after 60 days and then closethem once they have been stale for 15 days.Pull-Requests: It will mark pull-requests as stale after 90 days and then closethem once they have been stale for 15 days.https://github.com/actions/staleCloses:#1649
@nejchnejch merged commit9896340 intomainJan 7, 2022
@nejchnejch deleted the jlvillal/stale branchJanuary 7, 2022 18:16
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@max-wittigmax-wittigmax-wittig approved these changes

@nejchnejchAwaiting requested review from nejch

Assignees

@JohnVillalovosJohnVillalovos

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Set up an action to lock very old closed issues
3 participants
@JohnVillalovos@nejch@max-wittig

[8]ページ先頭

©2009-2025 Movatter.jp