HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
isaacs
github
OPEN SOURCE2013–2026
isaacs / github · Archived

github

Just a place to track issues and feature requests that I have for github

Explore on GitHubRead Hacker News discussions
87Distinct people
101Mentions
0Explicit recommenders
2.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Just a place to track issues and feature requests that I have for github

GitHub

Where it is used

No documented product use was verified in the last source check.

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, 6:01:08 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 year101 dated mentions

Observed mentions: 2013-06-04 17:52:47 UTC to 2026-04-29 03:42:11 UTC.

051015202013-01-01 00:00:00 UTC to 2014-01-01 00:00:00 UTC (exclusive): 4 mentions; 3 submissions, 1 comments20132014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 9 mentions; 3 submissions, 6 comments2015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 13 mentions; 5 submissions, 8 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 18 mentions; 3 submissions, 15 comments2017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 15 mentions; 3 submissions, 12 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 7 mentions; 1 submissions, 6 comments20192020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 9 mentions; 4 submissions, 5 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 9 mentions; 4 submissions, 5 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 5 mentions; 1 submissions, 4 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

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
20132013-01-01 00:00:00 UTC2014-01-01 00:00:00 UTC431
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC936
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC1358
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC18315
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC725
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC15312
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC716
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC945
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC945
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC303
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC514
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC101

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
IMPORTANT NOTE: GITHUB NOW HAS AN OFFICIAL FEEDBACK REPOSITORY. OPEN A DISCUSSION THERE TO ASK QUESTIONS OR DISCUSS BUGS. THIS REPO IS DEPRECATED. Issues for GitHub What this repository is about This is not the actual repository for the GitHub website. I'm not affiliated with GitHub in any way, except that I use it all day long, and almost all my code is hosted there. UPDATE: as of April 2020, with the acquisition of npm, Inc. by GitHub, I am a GitHub employee. I remain focused on the npm/cli project, and any opinions expressed here belong to the person expressing them at the time they were expressed, and should not be taken as official GitHub policy in any way. I still use GitHub all day long, and almost all my code is still hosted there. Issues and feature requests posted to GitHub are not stored in any publicly available location, so I find that I quickly lose track of the things that I've sent them. For GitHubbers If you are a GitHubber, and you would like to respond and close issues on this repository, please let me (or one of the other collaborators) know, and we'll add you as a collaborator. Alternatively, you could use some secret GitHub internal APIs to get access, if you have such things. If you want to know what people are asking for or ask for them to provide details about use cases. Then head over to the issues list. If you have an issue or feature request for GitHub Search for existing issues If you did not find any existing issue for your topic, post a new issue Additionally, please email support@github.com because this repo is strictly for our own (unofficial) tracking purposes. Make sure to send GitHub the issue URL at the end of the message so that they can more easily find updates and further comments here. If GitHub replies, (and they usually do, quickly) and if it is not a confidential matter like a security disclosure, add their reply to the issue so that other users know what their official response was. Upvoting existing issues Upvote existing issues with thumbs up 👍. Please do not add +1 comments. If you merely want to +1 an issue (isaacs/github#9), please also send an email to support@github.com to register your interest. Be sure to include a link to the tracking issue that was filed. See more in CONTRIBUTING.md Issue closing policy Issues will only be closed once GitHub implements / fixes them, or explicitly says WONTFIX, which almost never happens nowadays. Issues may take a long time (forever) to be fixed, so make sure that you are ready to keep them around on your /issues list for a long time. See also Dear GitHub Statement of Intent This repository is created in a spirit of positive intent and community good will. I have more love in my heart for GitHub than anyone probably ought to for any website. They've changed the face of open source, and enabled amazing things to happen. I've personally benefited quite a bit from those amazing things, and my life is much better as a direct result. I'm very thankful to GitHub, and the great work they do. When I shake my fists in frustration, it's only because they are so good that I spend countless hours being productive on their website, and even minor problems seem to jump out. Trolling, disparaging remarks about GitHub, or even just unproductive kvetching, will not be tolerated. Those comments will be deleted and the users blocked. We're here to help each other, and the company that does so much for us. <3 --isaacs
Read the full README on GitHub

What Hacker News says

7 sources
tony101·Sep 12, 2017
Note that in this setup, the connection between Cloudflare and GitHub is plaintext / not secure, because by default Cloudflare uses "Flexible SSL". It is possible to make it more secure by changing the setting to "Full SSL (non-strict)", which encrypts the connection between Cloudflare and GitHub against passive attacks but not active interception. Unfortunately, GitHub pages does not work with Cloudflare's "Full SSL (strict)" option. Cloudflare SSL Options: https://support.cloudflare.com/hc/en-us/articles/200170416-W... Example of attack between Cloudflare and origin: https://medium.com/@karthikb351/airtel-is-sniffing-and-censo... GitHub issue page: https://github.com/isaacs/github/issues/156
In Building a fast, secured and free static site in less than three hours
chronial·Jun 19, 2017
> Please be honest: did you see it work at least once? No, I never tried this before. I was just guessing based on the client error message. But a quick look in the source reveals that this is indeed a server setting that defaults to false: https://git-scm.com/docs/git-config#git-config-uploadpackall... If fetching non-tagged, non-branchhead commits is actually a frequent use case for you, you could ask github whether they might change their config. You are not the first person to want this: https://github.com/isaacs/github/issues/436 > It seems we're back to square one. Almost :). You said: > Bazaars allows remotely fetching one single revision from a repo, without requiring to download the whole history. You can't do this with git. As it turns out that is not correct – git can absolutely do that. But the two biggest hosters don't allow
Read the rest
it.
In Inkscape Moves to GitLab

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.