Skip to content

Conversation

@dciangot
Copy link
Contributor

@ericvaandering I don't know if this can help. But in case I put here the changes needed to automatically manage stale issues and PR. Hopefully pushing toward either closing it or update the status

@ericvaandering
Copy link
Member

I like the idea. So the "5" in the config refers to days after adding the stale label? Even so, I'd up that to at least 10. Not hard to have 5 days where people are generally not working.

Also, -1 on PR suggests PRs never get closed despite the text. Is that the intention?

@dciangot
Copy link
Contributor Author

dciangot commented Sep 8, 2023

all correct @ericvaandering
about the 10d before closing, it's fine with me.

- uses: actions/stale@v7
with:
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 10 days.'
stale-pr-message: 'This PR is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 10 days.'
Copy link
Member

Choose a reason for hiding this comment

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

Since we are not going to close PRs, I think the message should ask the originator to review it, not say it will be closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants