pytorch / pytorch/vision

Automate closing of scheduled workflows

Open
#5,290 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

module: ci module: datasets
Dominant language
Python
Stars
17.9k
Forks
7.3k
Avg merge
1d 15h
Merged PRs (30d)
13

Description

🚀 The feature

We need to currently close the Issues raised by our automated tests for datasets manually.

https://github.com/pytorch/vision/issues?q=is%3Aissue+is%3Aopen+Scheduled+workflow+failed ?

Sometimes they get bunched up or we forget to close them.

Motivation

The cronjob runs daily. So ideally we should be closing the issue the next day if it doesn't fail. (If it does fail anyway another issue is created).

I propose a simple GitHub action that closes only this issue once the issue gets stale by 3 days. The logic is that if the issue is open for 3 days.

  1. Everything is working fine and hence we don't have a problem to close it. (It was one off error)
  2. There is another issue which is newer that supersedes this old issue.

So we should be fine closing it.

Pitch

I think a simple GitHub action can do this job. Would need to investigate but think that technically it's very much possible.

Additional context

I don't propose to extend this functionality to close all stale issues. An issue is well documented user feedback which is very valuable indeed. An old issue can be gem of resource for someone and keeping it open doesn't harm.

But for bot issues :( It isn't nice to be flooded with them being open :(

Some references

https://github.com/marketplace/actions/close-stale-issues

cc @pmeier @seemethere

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked Marketplace close-stale-issues action and the repository's GitHub Actions configuration. Define the workflow's behavior for scheduled-workflow failure issues, including the three-day threshold and the restriction to this issue type; done means eligible bot issues close automatically without affecting general stale issues.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.