HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
github
github-services
Ruby2010–2013
github / github-services · Archived

github-services

Legacy GitHub Services Integration

7Distinct people
7Mentions
0Explicit recommenders
1.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Legacy GitHub Services Integration

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, 11:56:56 AM 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 year7 dated mentions

Observed mentions: 2010-07-16 02:53:21 UTC to 2013-11-22 07:30:31 UTC.

012342010-01-01 00:00:00 UTC to 2011-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20102011-01-01 00:00:00 UTC to 2012-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20112012-01-01 00:00:00 UTC to 2013-01-01 00:00:00 UTC (exclusive): 4 mentions; 1 submissions, 3 comments2013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2013

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
20102010-01-01 00:00:00 UTC2011-01-01 00:00:00 UTC101
20112011-01-01 00:00:00 UTC2012-01-01 00:00:00 UTC101
20122012-01-01 00:00:00 UTC2013-01-01 00:00:00 UTC413
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC101

What Hacker News says

7 sources
I'm quoted in the article and I wanted to clear one thing up that was missing from it. When bots get reported to us by people using GitHub our support folks reach out to the bot account owner and encourage them to build a GitHub service[1] instead. As a service, the same functionality would still be available to everyone using GitHub, but it would be opt-in instead. A few months ago we heard from some developers of service integrations that beyond the existing API features, it would be handy to be able to provide a form of "status" for commits. We added the commit status API [2] in September to accommodate that. We're always open to feedback on how the API and service integrations can improve. The point is, GitHub services are a much better way to build integrations on GitHub. [1] https://github.com/github/github-services [2] https://gith
Read the rest
In GitHub Says ‘No Thanks’ to Bots — Even if They’re Nice
It would be cool if they extended the service hooks[1] to handle that. So then you could get the notification by Email, Notifo, Campfire, etc. (And I have some code that goes Notifo->Growl that I need to clean up and document.) Right now the service hooks are just for pushes. If I could say I want IRC to get notified about pull requests, new issues, and comments on issues, want to get emailed about new issues (note that that's a repeat) and comments on my commits, and want to get notified about pull requests (also a repeat), that would be awesome. I'm not sure how many people would want a crazy setup like that, but I could see wanting Campfire/IRC to get notified about more than just pushes. [1] http://github.com/github/github-services
In GitHub Notifications: Stars, please

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.