JakeHillion/nixpkgs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
674d77e68a
nixpkgs/.github/STALE-BOT.md
David Arnold 27510ad13f stale bot: TL;DR 
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>
2020-10-24 20:13:17 -07:00

3.1 KiB
Raw Blame History

Stale bot information

  • Thanks for your contribution!
  • To remove the stale label, just leave a new comment.
  • How to find the right people to ping? → git blame to the rescue! (or GitHub's history and blame buttons.)
  • You can always ask for help on our Discourse Forum or on the #nixos IRC channel.

Suggestions for PRs

  1. If it is unfinished but you plan to finish it, please mark it as a draft.
  2. If you don't expect to work on it any time soon, closing it with a short comment may encourage someone else to pick up your work.
  3. To get things rolling again, rebase the PR against the target branch and address valid comments.
  4. If you need a review to move forward, ask in the Discourse thread for PRs that need help.
  5. If all you need is a merge, check the git history to find and request reviews from people who usually merge related contributions.

Suggestions for issues

  1. If it is resolved (either for you personally, or in general), please consider closing it.
  2. If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough.
  3. If you still have interest in resolving it, try to ping somebody who you believe might have an interest in the topic. Consider discussing the problem in our Discourse Forum.
  4. As with all open source projects, your best option is to submit a Pull Request that addresses this issue. We ❤️ this attitude!

Memorandum on closing issues

Don't be afraid to close an issue that holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen--nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.

Useful GitHub search queries