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

Enable stalebot #2602

Closed
1 task done
marcphilipp opened this issue Apr 24, 2021 · 3 comments
Closed
1 task done

Enable stalebot #2602

marcphilipp opened this issue Apr 24, 2021 · 3 comments
Assignees
Milestone

Comments

@marcphilipp
Copy link
Member

marcphilipp commented Apr 24, 2021

In order to close obsolete issues without having to manually go through issues, we should enable Stalebot to comment on issues that haven't been updated in a certain timeframe. If nobody responds or attaches a certain label, i.e. the issue is no longer relevant, the bot will close it.

Proposed config

# Configuration for probot-stale - https://github.com/probot/stale
# Configuration options apply to both Issues and Pull Requests.
# We configure those individually to match our workflow (see `pulls:` and `issues:`)

pulls:
  # Number of days of inactivity before a Pull Request becomes stale
  daysUntilStale: 60

  # Number of days of inactivity before a Pull Request with the stale label is closed.
  # Set to false to disable. If disabled, Pull Request still need to be closed manually, but will remain marked as stale.
  daysUntilClose: 21

  # Comment to post when marking as stale. Set to `false` to disable
  markComment: >
    This pull request has been automatically marked as stale because it has not had recent activity.
    Given the limited bandwidth of the team, it will be closed if no further activity occurs.
    If you intend to work on this pull request, please reopen the PR.
    Thank you for your contributions.
  # Comment to post when closing a stale Pull Request.
  closeComment: >
    This pull request has been automatically closed due to inactivity.
    If you are still interested in contributing this, please ensure that
    it is rebased against the latest branch (usually `main`), all review
    comments have been addressed and the build is passing.
issues:
  daysUntilStale: 365

  # Number of days of inactivity before an Issue with the stale label is closed.
  # Set to false to disable. If disabled, issues still need to be closed manually, but will remain marked as stale.
  daysUntilClose: 21

  # Comment to post when marking as stale. Set to `false` to disable
  markComment: >
    This issue has been automatically marked as stale because it has not had recent activity.
    Given the limited bandwidth of the team, it will be automatically closed if no further
    activity occurs.
    Thank you for your contribution.
  # Comment to post when closing a stale Issue.
  closeComment: >
    This issue has been automatically closed due to inactivity. If you have a good use case for this
    feature, please feel free to reopen the issue.

# Only issues or pull requests with all of these labels are check if stale. Defaults to `[]` (disabled)
#onlyLabels: []

# Issues or Pull Requests with these labels will never be considered stale. Set to `[]` to disable
exemptLabels: []

# Set to true to ignore issues in a project (defaults to false)
exemptProjects: false

# Set to true to ignore issues in a milestone (defaults to false)
exemptMilestones: false

# Set to true to ignore issues with an assignee (defaults to false)
exemptAssignees: false

# Label to use when marking as stale
staleLabel: "status: stale"

# Comment to post when removing the stale label.
# unmarkComment: >
#   Your comment here.

# Limit the number of actions per hour, from 1-30. Default is 30
limitPerRun: 30

# Limit to only `issues` or `pulls`
# only: issues

Deliverables

  • Enable the bot using the above config
@marcphilipp
Copy link
Member Author

Tentatively slated for 5.8 M2 solely for the purpose of team discussion.

@marcphilipp
Copy link
Member Author

Team decision: Give the bot a try with the above config and review its activity and effectiveness after a few weeks.

@Marcono1234
Copy link
Contributor

please reopen the PR

please feel free to reopen the issue

Unfortunately that does not seem to be possible, users seem to only be able to reopen issues if they closed them themselves. And at the moment stalebot does not provide a solution for that yet either, see probot/stale#205.

Also for what it's worth, the current status of the stalebot app is not very clear, see probot/stale#349 and probot/probot.github.io#376.

runningcode pushed a commit to runningcode/junit5 that referenced this issue Feb 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants