Skip to content

CI: Process stale issues four times per day#116857

Merged
hugovk merged 1 commit intopython:mainfrom
hugovk:stale-4x-per-day
Mar 16, 2024
Merged

CI: Process stale issues four times per day#116857
hugovk merged 1 commit intopython:mainfrom
hugovk:stale-4x-per-day

Conversation

@hugovk hugovk merged commit 259dbc4 into python:main Mar 16, 2024
@hugovk hugovk deleted the stale-4x-per-day branch March 16, 2024 17:59
vstinner pushed a commit to vstinner/cpython that referenced this pull request Mar 20, 2024
adorilson pushed a commit to adorilson/cpython that referenced this pull request Mar 25, 2024
diegorusso pushed a commit to diegorusso/cpython that referenced this pull request Apr 17, 2024
@merwok
Copy link
Copy Markdown
Member

merwok commented Apr 10, 2026

I don’t know where to discuss this stale bot.

Is the label that useful, given the possibility of sorting by last-updated?

If yes, can the comment be skipped, to avoid unhelpful notification? (They are only helpful on repos that auto-close valid issues just because of time elapsed, which is annoying too.)

@hugovk
Copy link
Copy Markdown
Member Author

hugovk commented Apr 10, 2026

I don’t know where to discuss this stale bot.

Perhaps a new core-workflow issue?

Is the label that useful, given the possibility of sorting by last-updated?

I'm using it as an opportunity to check the current status of old PRs, and consider whether they're still needed. For example, on one I reminded the author to sign the CLA or we'll need to close it, and added pending to follow up.

If yes, can the comment be skipped, to avoid unhelpful notification? (They are only helpful on repos that auto-close valid issues just because of time elapsed, which is annoying too.)

We used to autoclose stale PRs with no CLA. This needs reimplementing: python/core-workflow#441.

@StanFromIreland
Copy link
Copy Markdown
Member

We used to autoclose stale PRs with no CLA. This needs reimplementing: python/core-workflow#441.

Should we have a system where we convert old PRs that need a little update to 'easy' issues for someone to pick up? For example #30097, which was marked stale today. The author abandoned it, but the change still needs to be done.

@hugovk
Copy link
Copy Markdown
Member Author

hugovk commented Apr 10, 2026

Close the PR, create an issue.

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.

4 participants