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

Update stalebot message to explain how to keep an issue alive #258

Merged
2 commits merged into from
Apr 18, 2023

Conversation

ghost
Copy link

@ghost ghost commented Apr 18, 2023

Description

The current messaging doesn't provide information about how to un-stale an issue or the time scales for when the issue will move into stale/closed. This commit updates the messaging to make it more approachable.

Type of Change

[ ] Bug Fix
[ ] New Feature
[ ] Breaking Change
[ ] Refactor
[X] Documentation
[ ] Other (please describe)

Checklist

  • I have read the contributing guidelines
  • Existing issues have been referenced (where applicable)
  • I have verified this change is not present in other open pull requests
  • Functionality is documented
  • All code style checks pass
  • New code contribution is covered by automated tests
  • All new and existing tests pass

The current messaging doesn't provide information about how to un-stale
an issue or the time scales for when the issue will move into
stale/closed. This commit updates the messaging to make it more
approachable.
@ghost ghost self-requested a review as a code owner April 18, 2023 07:55
@ghost ghost enabled auto-merge (rebase) April 18, 2023 08:07
@ghost ghost merged commit a4a2389 into main Apr 18, 2023
5 checks passed
@ghost ghost deleted the stalebot_messaging branch April 18, 2023 08:25
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants