| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
| |
Tweak TL;DR a little to provide an empathetic springboard
to where we want people to land.
|
| | |
|
| |
|
|
|
|
|
|
| |
moves all the information to the Markdown document that we can
dynamically update and tries to make things more concise and scannable.
Co-authored-by: Ryan Mulligan <ryan@ryantm.com>
Co-authored-by: Travis A. Everett <travis.a.everett@gmail.com>
|
| | |
|
| |
|
|
|
|
|
|
|
| |
As somewhat discussed at: https://git.io/JJkRa, make the bot's message a
bit more instructive, and clearer as for what it will and won't do, so
random contributors will have a better idea what this is about.
Also: Split stale issues' and PRs' messages because each should
suggest different actions to do.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before this, the message being written is:
```
Thank you for your contributions.
This has been automatically marked as stale because it has had no activity for 180 days.
If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity.
Here are suggestions that might help resolve this more quickly:
1. Search for maintainers and people that previously touched the
related code and @ mention them in a comment.
2. Ask on the [NixOS Discourse](https://discourse.nixos.org/). 3. Ask on the [#nixos channel](irc://irc.freenode.net/#nixos) on
[irc.freenode.net](https://freenode.net).
```
Co-authored-by: zowoq <59103226+zowoq@users.noreply.github.com>
.github/stale.yml: fix newlines
|
| | |
|
|
|
The configuration added is taken from RFC 0051, and is the first step
toward implementing it. Next, we will have to enable the stale bot by
installing the GitHub application.
https://github.com/NixOS/rfcs/blob/master/rfcs/0051-mark-stale-issues.md
|