-
-
Notifications
You must be signed in to change notification settings - Fork 14.9k
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
stale bot: even more TL;DR #101320
stale bot: even more TL;DR #101320
Conversation
Excellent! Thanks also for the rewordings! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Formatting Oversight
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks Great to me. Good thinking!
bb06507
to
1e1c715
Compare
I resolved my formatting mistake and added a Thank you to the top. cc @abathur who cares about this too. |
I either didn't stay in the loop or have simply forgotten, but I didn't realize the current messages were this big. It's good to give information, but I agree the message is trying to do much work. What sort of feedback/edits are you looking for? I don't have time to read everything or copyedit the manual section just this moment, but I think I'd like to at least make a suggested edit that rounds the corners of the new message later today. |
@abathur I'm planning to merge this tomorrow, so if your suggestions don't happen by then, feel free to do a separate PR! |
@abathur Sorry, I didn't answer your question. I was looking for proof reading/copy editing, since the text changed a lot. The most important part to get right is the short markComment part though, since we can dynamically change the other part. |
I'll try to double-dip some build time to look at it this evening :) Edit: I didn't explain most of these, but feel free to haggle or ask for reasoning. |
squashed all those commits into one |
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>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good to merge!
I think this needs at least some form of short introduction. Just linking to another document without any other information seems... bad, to me. See #85956 (comment) -- just dropping a link doesn't feel like a good user experience to me, at least without some kind of short explanation. |
@cole-h Thanks for the feedback! Here's our reasons for making it super short:
How does that sit with you? Do you have a suggestion or what to change? |
Maye a compromise could be:
|
@ryantm I definitely agree with all of your reasoning, but I also think there ought to be a small "springboard" (if you will), as @blaggacao suggested. I would lean more towards a message like the following:
or something similar. It gives a "why", and then links to the document, instead of just dropping a link and saying "cya". |
→ #101781 |
Am I missing something or does this ... not actually tell the user how to remove the stale tag from an issue that is still important? |
@colemickens the doc it links to says "To remove the stale label, just leave a new comment" very prominently. |
I don't know why I glazed over that and went straight to "suggestions for PRs" (and then skimmed the text for any |
Continuation of #100462 since I couldn't figure out how to make a PR against @blaggacao's repo.
The goal here is to make the stale bot's message super short, and direct people to a documentation page that we can update over time.