Skip to content

Create issue template to redirect people to official GitHub community#295

Open
aspiers wants to merge 1 commit into
dear-github:masterfrom
aspiers:patch-1
Open

Create issue template to redirect people to official GitHub community#295
aspiers wants to merge 1 commit into
dear-github:masterfrom
aspiers:patch-1

Conversation

@aspiers
Copy link
Copy Markdown

@aspiers aspiers commented Mar 22, 2018

UPDATE: since https://github.com/isaacs/github was (wrongly, IMHO) archived, there is an official GitHub community discussion forum, so dear-github should redirect to that now.

Original text below:


This repository was created for a specific purpose, which was fulfilled back in 2016. However people are still submitting issues about GitHub to the repository's issue tracker. This effectively fragments and weakens the GitHub community, because https://github.com/isaacs/github was already established in 2013 for the same purpose, and has acquired very significant momentum since then. It is more efficient for the community to pool its efforts in a single place, so make an issue template which explains the current situation and encourages people to submit issues to isaacs instead of here.

This partially addresses #207. When combined with a PR auto-closer bot as suggested in isaacs/github#1191, the combination could be considered as a full solution for #207.

This repository was created for a specific purpose, which was
fulfilled back in 2016.  However people are still submitting issues
about GitHub to the repository's issue tracker.  This effectively
fragments and weakens the GitHub community, because

    https://github.com/isaacs/github

was already established in 2013 for the same purpose, and has acquired
very significant momentum since then.  It is more efficient for the
community to pool its efforts in a single place, so make an issue
template which explains the current situation and encourages people
to submit issues to isaacs instead of here.

This partially addresses dear-github#207.  When combined with a PR auto-closer
bot as suggested in

    isaacs/github#1191

the combination could be considered as a full solution for dear-github#207.
@koenpunt
Copy link
Copy Markdown

Probably better to just archive this repository, which will make it read-only

@aspiers
Copy link
Copy Markdown
Author

aspiers commented Mar 26, 2018

@koenpunt Archiving sounds like a good idea, but there still needs to be a redirect to
https://github.com/isaacs/github/ so that people know where to track issues.

@aspiers
Copy link
Copy Markdown
Author

aspiers commented Aug 2, 2018

Can a maintainer review this please?

@aspiers aspiers mentioned this pull request Aug 2, 2018
@fatso83
Copy link
Copy Markdown

fatso83 commented Feb 12, 2026

The isaacs repo is long gone and Github has official community feedback

bilde

Check out https://github.com/community

@aspiers aspiers changed the title Create issue template to redirect people to isaacs repo Create issue template to redirect people to official GitHub community Mar 4, 2026
@aspiers
Copy link
Copy Markdown
Author

aspiers commented Mar 4, 2026

Updated title and description accordingly.

@TPS
Copy link
Copy Markdown

TPS commented Mar 4, 2026

@aspiers Honestly, since your original issue, this repo has become stale/obsolete, attracting spam, mostly. It's probably time to archive it (since enough time now) in favor of the official, Isaacs', knowing it can always be unarchived later, e.g., whenever GitHub reaches enshittification lvl 3, since we're pretty much already @ lvl 2.

@aspiers
Copy link
Copy Markdown
Author

aspiers commented Mar 4, 2026

For me it reached level 3 the moment they implemented my worst case scenario of community neglect / takeover despite my very polite request to do otherwise. I'm very grateful there are many good FOSS alternatives like GitLab and others, but sadly this hasn't prevented the whole world from unnecessarily locking ourselves into huge reliance on GitHub. A real own goal 😢

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants