HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
notwaldorf
github-canned-responses
JavaScript2016–2016
notwaldorf / github-canned-responses

github-canned-responses

:zzz: (inactive) Because copy pasting isn't that great.

2Distinct people
2Mentions
0Explicit recommenders
368GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

:zzz: (inactive) Because copy pasting isn't that great.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour2 dated mentions

Observed mentions: 2016-03-29 19:55:24 UTC to 2016-03-29 21:53:15 UTC.

012016-03-29 19:00:00 UTC to 2016-03-29 20:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 29, 19:002016-03-29 20:00:00 UTC to 2016-03-29 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 29, 20:002016-03-29 21:00:00 UTC to 2016-03-29 22:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 29, 21:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 29, 19:002016-03-29 19:00:00 UTC2016-03-29 20:00:00 UTC101
Mar 29, 20:002016-03-29 20:00:00 UTC2016-03-29 21:00:00 UTC000
Mar 29, 21:002016-03-29 21:00:00 UTC2016-03-29 22:00:00 UTC101

What Hacker News says

2 sources
The implication here, isn't so much that what was created was new, it's "Would this feature had been created had somebody else not shown GitHub a better way?" Since the commit history for https://github.com/notwaldorf/github-canned-responses/commit... is fairly new, it's easy to believe this feature was in GitHub's pipeline for a while. If this wasn't the case, it can sting from a brand perception point of view. GitHub is suppose to be synonymous with innovation, and if you start getting called out for copying, no matter how trivial, it will devalue your brand over time. The question now is, how closely is GitHub looking at something like this: https://github.com/stefanbuck/awesome-browser-extensions-for... and other similar Chrome extensions. Right now, they are in a damned if they do and damned if they don't, as the result of the dear G
Read the rest
itHub letter.
In Saved Replies

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.