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

Introduce Workflow to Manage Stale Issues #7737

Merged
merged 1 commit into from
Jan 3, 2024

Conversation

drew2a
Copy link
Contributor

@drew2a drew2a commented Nov 30, 2023

This PR introduces a new GitHub Actions workflow for managing stale issues in our repository. Key features of this workflow include:

  • Automatically marking issues as stale after 60 days of inactivity.
  • Not auto-closing stale issues; instead, they will require manual review for closure.

This addition aims to improve our issue tracking and ensure that open issues remain relevant and actively discussed. It also allows for greater flexibility in managing community contributions and feedback.

Adresses: #6135
Ref:

@drew2a drew2a force-pushed the feature/stale-actions branch from 762c710 to a983f49 Compare December 8, 2023 12:42
@drew2a drew2a changed the title Add workflow to close stale issues Introduce Workflow to Manage Stale Issues Dec 8, 2023
@drew2a drew2a marked this pull request as ready for review December 8, 2023 12:46
@drew2a drew2a requested review from a team, xoriole and synctext and removed request for a team December 8, 2023 12:46
Copy link
Member

@synctext synctext left a comment

Choose a reason for hiding this comment

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

All good! btw we have numerous unused labels. Use-them-or-delete them seems good for cleanup.

This commit adds a new workflow file, `stale.yml`, which is responsible for closing stale issues and pull requests. The workflow is triggered daily at 1:30 AM UTC using a cron schedule. It runs on the latest version of Ubuntu.

The `stale` job within the workflow uses the `actions/stale@v8` action. It includes several configuration options:
- A message is set for stale issues that have not seen activity for 60 days.
- A label, "status: stale", is applied to mark the issue as stale.
- Only issues with the label "status: can't reproduce" are considered for staleness.
- The number of days before an issue becomes stale is set to 60.
- The number of days before a stale issue gets closed automatically is set to -1, indicating no automatic closure.

These changes aim to improve issue management by identifying and closing inactive or unactionable issues.
@drew2a drew2a force-pushed the feature/stale-actions branch from a983f49 to 44cee2f Compare January 3, 2024 15:34
@drew2a drew2a merged commit 8c2f12c into Tribler:main Jan 3, 2024
15 checks passed
@drew2a drew2a deleted the feature/stale-actions branch January 3, 2024 15:36
@drew2a
Copy link
Contributor Author

drew2a commented Jan 3, 2024

@synctext, I agree about the unused labels. Groups should also be cleaned up at some point: https://github.com/orgs/Tribler/teams

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

Successfully merging this pull request may close these issues.

3 participants