Awesome. Now I can add +1 comments with just a click.
You're able to add +1 through their recent GitHub Reactions update now: https://github.com/blog/2119-add-reactions-to-pull-requests-...
Except it doesn't do notifications like a comment does...
Saved Replies
71–80 of 91 posts
Re: Saved Replies
#72Awesome. Now I can add +1 comments with just a click.
+1
Re: Saved Replies
#73They basically took the idea from this Chrome extension: https://chrome.google.com/webstore/detail/github-canned-resp...
Next Chrome Extension to take ideas from: https://chrome.google.com/webstore/detail/github-module-brow...
Re: Saved Replies
#74Now _this_ is the kind of feature that really, really, really helps me. This will make my life immediately, measurably better.
FYI, there are lots of tools that bring this functionality to any application or website, such as https://www.trankynam.com/atext/ or http://www.yesware.com/ for Gmail. Sharing templates isn't the bottleneck, just inserting them. No need to wait for Github to build it!
Yeah, as mentioned down thread, those are nice, but are too often tied to a particular computer.
I generally prefer the web for almost all things.
Re: Saved Replies
#75Earlier quoted context omitted.
This is where CONTRIBUTING.md comes in. If a project doesn't want Issues to be used for support, then it should mention it there. Whether people actually read it is another story :(
Yeah this is actually my canned response on one of my own projects, and I'm tired of copying and pasting it. Nobody reads CONTRIBUTING.md
In our issues template, we start it with:
"GitHub issues are for bugs / installation problems / feature requests. For general support from the community, see [StackOverflow](link)"
However, we still get plenty of issues filed that are more appropriate for StackOverflow, so not sure there's anything technical you can do without integrating more closely with StackOverflow :)
Re: Saved Replies
#76It's nice that only you can see your reply titles.
--
Asshole
[... a very polite request for the user to stop trolling ...]
Re: Saved Replies
#77Earlier quoted context omitted.
You're able to add +1 through their recent GitHub Reactions update now: https://github.com/blog/2119-add-reactions-to-pull-requests-...
That's the joke :)
Re: Saved Replies
#78Now they just need a "on vacation" button.
The done thing on bugzilla.mozilla.org seems to be changing your display name to include "vacation" or similar, but I haven't seen much of that on GitHub.
Re: Saved Replies
#79Earlier quoted context omitted.
It has nothing to do with the popularity of the repository, really, but more with the quality of the issues. >>> I would hate an automatic reply for filling an issue for a small library or such. If the issue is lets say not reproducible because of lack of information provided, does it really matter if the response was typed out by hand? The response would be the same, give or take a couple of words.
The maintainer could see that, due to the nature of the issue, maybe the user OS would matter. Or maybe there's another version on the horizon that changes completely the functionally in topic. A hand crafted reply asking some curated questions/suggestions is not the same from an automatic "not enough information". It's not about typing, it's about making a conversation.
But this is a massive waste of time.
For example, this past weekend I triaged over 600 issues on a project that sees a lot of maintainer churn (ui-select for Angular) - the low quality issues is a lot of the problem, and maintainers waste a lot of mental energy when they have to focus on a lot of issues where the reporter didn't do the basic level of due diligence.
If this feature was released beforehand, it probably would have saved me a couple of hours :( .
Re: Saved Replies
#80Earlier quoted context omitted.
The maintainer could see that, due to the nature of the issue, maybe the user OS would matter. Or maybe there's another version on the horizon that changes completely the functionally in topic. A hand crafted reply asking some curated questions/suggestions is not the same from an automatic "not enough information". It's not about typing, it's about making a conversation.
But this is a massive waste of time. For example, this past weekend I triaged over 600 issues on a project that sees a lot of maintainer churn (ui-select for Angular) - the low quality issues is a lot of the problem, and maintainers waste a lot of mental energy when they have to focus on a lot of issues where the reporter didn't do the basic level of due diligence. If this feature was released beforehand, it probably…
600 issues is a lot, I consider that a popular repository.
I'm not against the feature, I think it's (for big repos) a necessary evil.