From 557e9375333861814b4d4555259c101aa3d79671 Mon Sep 17 00:00:00 2001 From: Kevin Ebaugh Date: Tue, 18 Feb 2020 14:25:49 -0500 Subject: [PATCH 1/9] Update README.md Emails to support@github.com bounce now, so updating the contact method in the README. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 77f6280..114a114 100644 --- a/README.md +++ b/README.md @@ -17,7 +17,7 @@ want to know what people are asking for, or ask for them to provide details about use cases etc, then head over to the issues list. Post an issue if you have an issue or feature request for GitHub. -**But you should also email support@github.com, since this repo is +**But you should also [contact GitHub](https://support.github.com/contact), since this repo is strictly for our own (unofficial) tracking purposes.** If they reply, (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 From 81f7665e8b8d88fbca1a9753fecffaa38b8200ad Mon Sep 17 00:00:00 2001 From: Kristian Date: Fri, 24 Apr 2020 00:52:44 +0000 Subject: [PATCH 2/9] Replace support@github.com with support.github.com (#1738) * Replace support@github.com with support.github.com Suggest filing feedback, issues and feature requests through GitHubs support.github.com page as they no longer allow support requests to be opened through their email. Support requests to support@github.com will automatically be responded with an answer telling you to file a request over at https://support.github.com, at least as of current date (February, 2020). * Replace support@github.com in CONTRIBUTING.md Replace emails to support@github.com with filing reports on support.github.com instead. See commit e586e11ac0652db5630ff9a23c2628ccce413022 info. Co-authored-by: TPS --- CONTRIBUTING.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index a1c5224..d6d27ed 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -6,8 +6,8 @@ Please see the README.md and [isaacs/github#6](https://github.com/isaacs/github/issues/6) for the reasons why this repository exists. -If you file an issue in this repository, be sure to also email -support@github.com and include a link to the issue you have created. Also be +If you file an issue in this repository, be sure to also provide feedback to github through their support +page [here](https://support.github.com/contact/feedback) and include a link to the issue you have created. Also be sure to add as a comment to your issue any response(s) you receive from GitHub regarding your issue. From 81d5cae183fb9734212197f275ebfb41a0fc3acd Mon Sep 17 00:00:00 2001 From: TPS Date: Thu, 23 Apr 2020 21:24:42 -0400 Subject: [PATCH 3/9] Mostly, cleanup last obsolete contact link Update some other links & capitalization while I'm here. --- CONTRIBUTING.md | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index d6d27ed..c093107 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -2,18 +2,16 @@ **This is not the actual repository for the GitHub website.** -Please see the README.md and +Please see the README.md & [isaacs/github#6](https://github.com/isaacs/github/issues/6) for the reasons why this repository exists. -If you file an issue in this repository, be sure to also provide feedback to github through their support -page [here](https://support.github.com/contact/feedback) and include a link to the issue you have created. Also be +If you file an issue in this repository, be sure to also provide feedback to GitHub through their support +page [here](https://support.github.com/contact/feedback), including a link to the issue you have created. Also be sure to add as a comment to your issue any response(s) you receive from GitHub regarding your issue. -If you merely want to +1 an issue -([isaacs/github#9](https://github.com/isaacs/github/issues/9)) please also send -an email to support@github.com to register your interest. Be sure to also -include a link to the tracking issue that was filed. +If you merely want to [+1 an issue](https://github.blog/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/), please also contact GitHub via their support +page [here](https://support.github.com/contact/feedback) to register your interest, including a link to the tracking issue that was filed. -Please don't write +1 comments, use the thumbs up reaction instead. +[Please don't write +1 comments, use the thumbs up reaction instead.](https://github.blog/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) From 3d7de6954867e3a426c6319a749c564f7f3986ba Mon Sep 17 00:00:00 2001 From: isaacs Date: Tue, 25 Aug 2020 10:34:47 -0700 Subject: [PATCH 4/9] kind of affiliated, actually --- README.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 114a114..e186af4 100644 --- a/README.md +++ b/README.md @@ -2,8 +2,16 @@ **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. +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](https://blog.npmjs.org/post/612764866888007680/next-phase-montage), +I am a GitHub employee. I remain focused on the +[npm/cli](https://github.com/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 From 790cf4b51b4f921aaca03ee46cff6a5fddb19578 Mon Sep 17 00:00:00 2001 From: Sybille Peters Date: Tue, 6 Oct 2020 02:18:11 +0200 Subject: [PATCH 5/9] Structure README.md (#1852) * Structure README.md - reorder the part about creating issues and add a numbered list for better readability - add subheaders in README.md - link to CONTRIBUTING.md - Add information about how to upvote issues * Improve wording in README --- README.md | 46 ++++++++++++++++++++++++++++++++-------------- 1 file changed, 32 insertions(+), 14 deletions(-) diff --git a/README.md b/README.md index 114a114..225e40e 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,7 @@ # 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 @@ -9,22 +11,38 @@ 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. Or maybe 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 etc, then head over to the issues list. - -Post an issue if you have an issue or feature request for GitHub. -**But you should also [contact GitHub](https://support.github.com/contact), since this repo is -strictly for our own (unofficial) tracking purposes.** If they reply, -(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 can know what their official response was. - -Send GitHub the issue URL at the end of the message so that they can -more easily find updates and further comments here. +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 + +1. Search for existing [issues](https://github.com/isaacs/github/issues) +2. If you did not find any existing issue for your topic, post a new issue +3. **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. +4. 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 :thumbsup:. Please do not add +1 comments. + +If you merely want to +1 an issue +([isaacs/github#9](https://github.com/isaacs/github/issues/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](https://github.com/isaacs/github/blob/master/CONTRIBUTING.md) + +## Issue closing policy Issues will only be closed once GitHub implements / fixes them, or explicitly says WONTFIX, which almost never happens nowadays. From 1c46288ce8eab5ba9661cf18459116dfca6a9c2f Mon Sep 17 00:00:00 2001 From: Levi Lesches Date: Tue, 29 Jun 2021 21:22:46 -0400 Subject: [PATCH 6/9] Added notice of repo deprecation Let's also archive the repo, shall we? --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 5a797e2..a9d8aae 100644 --- a/README.md +++ b/README.md @@ -1,3 +1,5 @@ +## IMPORTANT NOTE: GITHUB NOW HAS [AN OFFICIAL FEEDBACK REPOSITORY](https://github.com/github/feedback/discussions/categories/general-feedback). OPEN A DISCUSSION THERE TO ASK QUESTIONS OR DISCUSS BUGS. THIS REPO IS DEPRECATED. + # Issues for GitHub ## What this repository is about From 4bf7c2bc10f46585a204970be6c2835725013d46 Mon Sep 17 00:00:00 2001 From: Michelle Merrill <73917114+michellemerrill@users.noreply.github.com> Date: Thu, 1 Jul 2021 20:33:22 -0700 Subject: [PATCH 7/9] Create main.yml test --- .github/workflows/main.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 .github/workflows/main.yml diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml new file mode 100644 index 0000000..3ccfdc3 --- /dev/null +++ b/.github/workflows/main.yml @@ -0,0 +1,18 @@ +name: Issue Autoresponse + +on: + issues: + types: [opened] + +jobs: + auto-response: + runs-on: ubuntu-latest + + steps: + - uses: michellemerrill/add-autoresponse@master + env: + GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} + with: + respondableId: ${{ github.event.issue.node_id }} + response: "GitHub staff are eager to continue in conversations and knowledge-sharing with you. We invite you to head over to [Feedback Discussions](https://github.com/github/feedback/discussions) and share your product feedback and questions [directly](https://github.com/isaacs/github#important-note-github-now-has-an-official-feedback-repository-open-a-discussion-there-to-ask-questions-or-discuss-bugs-this-repo-is-deprecated) with us. Once you have added your thoughts in Feedback Discussions, we ask that you close this newly-created issue. Otherwise, we will keep this issue open for the next 7 days, then will close it." + author: ${{ github.event.issue.user.login }} From 553c7ac15b8b38159302044f433a343a181dce73 Mon Sep 17 00:00:00 2001 From: Michelle Merrill <73917114+michellemerrill@users.noreply.github.com> Date: Thu, 1 Jul 2021 20:45:24 -0700 Subject: [PATCH 8/9] Delete main.yml Removed test --- .github/workflows/main.yml | 18 ------------------ 1 file changed, 18 deletions(-) delete mode 100644 .github/workflows/main.yml diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml deleted file mode 100644 index 3ccfdc3..0000000 --- a/.github/workflows/main.yml +++ /dev/null @@ -1,18 +0,0 @@ -name: Issue Autoresponse - -on: - issues: - types: [opened] - -jobs: - auto-response: - runs-on: ubuntu-latest - - steps: - - uses: michellemerrill/add-autoresponse@master - env: - GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} - with: - respondableId: ${{ github.event.issue.node_id }} - response: "GitHub staff are eager to continue in conversations and knowledge-sharing with you. We invite you to head over to [Feedback Discussions](https://github.com/github/feedback/discussions) and share your product feedback and questions [directly](https://github.com/isaacs/github#important-note-github-now-has-an-official-feedback-repository-open-a-discussion-there-to-ask-questions-or-discuss-bugs-this-repo-is-deprecated) with us. Once you have added your thoughts in Feedback Discussions, we ask that you close this newly-created issue. Otherwise, we will keep this issue open for the next 7 days, then will close it." - author: ${{ github.event.issue.user.login }} From f6fc600746d6fba5056b8b53e4d28b0141b78a1b Mon Sep 17 00:00:00 2001 From: Michelle Merrill <73917114+michellemerrill@users.noreply.github.com> Date: Mon, 12 Jul 2021 13:41:36 -0700 Subject: [PATCH 9/9] Add auto response workflow --- .github/workflows/add-autoresponse.yml | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) create mode 100644 .github/workflows/add-autoresponse.yml diff --git a/.github/workflows/add-autoresponse.yml b/.github/workflows/add-autoresponse.yml new file mode 100644 index 0000000..cb4bb15 --- /dev/null +++ b/.github/workflows/add-autoresponse.yml @@ -0,0 +1,18 @@ +name: Issue Autoresponse + +on: + issues: + types: [opened] + +jobs: + auto-response: + runs-on: ubuntu-latest + + steps: + - uses: derekprior/add-autoresponse@master + env: + GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} + with: + respondableId: ${{ github.event.issue.node_id }} + response: "_GitHub staff are eager to continue in conversations and knowledge-sharing with you. We invite you to head over to [Feedback Discussions](https://github.com/github/feedback/discussions) and share your product feedback and questions directly with us (noted [here](https://github.com/isaacs/github#important-note-github-now-has-an-official-feedback-repository-open-a-discussion-there-to-ask-questions-or-discuss-bugs-this-repo-is-deprecated)). Once you have added your thoughts in Feedback Discussions, we ask that you close this newly-created issue. Otherwise, we will keep this issue open for the next 7 days, then will close it._" + author: ${{ github.event.issue.user.login }}