[PR #1813] [MERGED] Add Discord Communities #1866

New Issue

Closed

opened 2025-11-06 16:02:05 -06:00 by GiteaMirror · 0 comments

GiteaMirror commented 2025-11-06 16:02:05 -06:00

Owner

Copy Link

📋 Pull Request Information

Original PR: https://github.com/sindresorhus/awesome/pull/1813
Author: @mhxion
Created: 6/28/2020
Status: ✅ Merged
Merged: 9/2/2020
Merged by: @sindresorhus

Base: main ← Head: patch-1

---

📝 Commits (3)

• 2474602 Add Programming Discord
• 5427945 Update repository URL
• 905b87a Update title

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 readme.md (+1 -0)

📄 Description

1. PR Reviewed: 1, 2, 3, 4
2. The list over 30-days old, has over 150 stars
3. I explained here why I'd used Notable Channels and badges instead a description for each entry.
4. Only table-pipe-alignment markdown lint rule was ignored because as the rule has mentioned, it was impossible to adapt the cell with variable number of images without making the code too messy.
5. I added this under Gaming due to Discord being more known for that.

https://github.com/mhxion/awesome-discord-communities#readme

Over the years hundreds of developer communities have made Discord their home for helping newcomers in tech, collaborating with open-source project users, and actively contributing by creating occasional programming challenges; this list aggregates the best of them. While existing helper-platforms like Stack Overflow, forums do their job well, they cannot be used for interacting live (debugging), Discord communities fill this major gap. The developer-friendlier the communities, the more productive collaboration is. As of now this list holds over 200 of them (and growing), each of them had gone through proper review policy, and other safety requirements, each carrying useful links; no other awesome Discord list exists to this extend until now. By nature this list is correlated with awesome-slack.

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.

Requirements for your pull request

• Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
• You have to review at least 2 other open pull requests.
  Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions.
• You have read and understood the instructions for creating a list.
• This pull request has a title in the format Add Name of List.
  • ✅ Add Swift
  • ✅ Add Software Architecture
  • ❌ Update readme.md
  • ❌ Add Awesome Swift
  • ❌ Add swift
  • ❌ Adding Swift
  • ❌ Added Swift
• Your entry here should include a short description about the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb.
  • ✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
  • ✅ - [Framer](…) - Prototyping interactive UI designs.
  • ❌ - [iOS](…) - Resources and tools for iOS development.
  • ❌ - [Framer](…)
  • ❌ - [Framer](…) - prototyping interactive UI designs
• Your entry should be added at the bottom of the appropriate category.
• The suggested Awesome list complies with the below requirements.

Requirements for your Awesome list

• Has been around for at least 30 days.
  That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
• Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it.
• Run awesome-lint on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please report it.
• The default branch should be named main, not master.
• Includes a succinct description of the project/theme at the top of the readme. (Example)
  • ✅ Mobile operating system for Apple phones and tablets.
  • ✅ Prototyping interactive UI designs.
  • ❌ Resources and tools for iOS development.
  • ❌ Awesome Framer packages and tools.
• It's the result of hard work and the best I could possibly produce.
  If you have not put in considerable effort into your list, your pull request will be immediately closed.
• The repo name of your list should be in lowercase slug format: awesome-name-of-list.
  • ✅ awesome-swift
  • ✅ awesome-web-typography
  • ❌ awesome-Swift
  • ❌ AwesomeWebTypography
• The heading title of your list should be in title case format: # Awesome Name of List.
  • ✅ # Awesome Swift
  • ✅ # Awesome Web Typography
  • ❌ # awesome-swift
  • ❌ # AwesomeSwift
• Non-generated Markdown file in a GitHub repo.
• The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
• Not a duplicate. Please search for existing submissions.
• Only has awesome items. Awesome lists are curations of the best, not everything.
• Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file.
• Includes a project logo/illustration whenever possible.
  • Either centered, fullwidth, or placed at the top-right of the readme. (Example)
  • The image should link to the project website or any relevant website.
  • The image should be high-DPI. Set it to maximum half the width of the original image.
• Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
• Includes the Awesome badge.
  • Should be placed on the right side of the readme heading.
    • Can be placed centered if the list has a centered graphics header.
  • Should link back to this list.
• Has a Table of Contents section.
  • Should be named Contents, not Table of Contents.
  • Should be the first section in the list.
  • Should only have one level of nested lists, preferably none.
• Has an appropriate license.
  • We strongly recommend the CC0 license, but any Creative Commons license will work.
    • Tip: You can quickly add it to your repo by going to this URL: https://github.com/<user>/<repo>/community/license/new?branch=master&template=cc0-1.0 (replace <user> and <repo> accordingly).
  • A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and Unlicense.
  • Place a file named license or LICENSE in the repo root with the license text.
  • Do not add the license name or text to the readme. GitHub already shows the license name at the top of the repo.
  • To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.
• Has contribution guidelines.
  • The file should be named contributing.md. Casing is up to you.
• Has consistent formatting and proper spelling/grammar.
  • The link and description are separated by a dash.
    Example: - [AVA](…) - JavaScript test runner.
  • The description starts with an uppercase character and ends with a period.
  • Consistent and correct naming. For example, Node.js, not NodeJS or node.js.
• Doesn't include a Travis badge.
  You can still use Travis for list linting, but the badge has no value in the readme.
• Doesn't include an Inspired by awesome-foo or Inspired by the Awesome project kinda link at the top of the readme. The Awesome badge is enough.

Go to the top and read it again.

---

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/sindresorhus/awesome/pull/1813 **Author:** [@mhxion](https://github.com/mhxion) **Created:** 6/28/2020 **Status:** ✅ Merged **Merged:** 9/2/2020 **Merged by:** [@sindresorhus](https://github.com/sindresorhus) **Base:** `main` ← **Head:** `patch-1` --- ### 📝 Commits (3) - [`2474602`](https://github.com/sindresorhus/awesome/commit/247460269ad9777832975920223cef17597653e9) Add Programming Discord - [`5427945`](https://github.com/sindresorhus/awesome/commit/542794599d4c10db6dd1975185038747badecf45) Update repository URL - [`905b87a`](https://github.com/sindresorhus/awesome/commit/905b87ae9f573eebcc6c49b645deb5ece31b660f) Update title ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `readme.md` (+1 -0) </details> ### 📄 Description <!-- Congrats on creating an Awesome list! 🎉 --> <!-- Please fill in the below placeholders --> 1. PR Reviewed: [__1__](https://github.com/sindresorhus/awesome/pull/1812#pullrequestreview-438679163), [__2__](https://github.com/sindresorhus/awesome/pull/1808#pullrequestreview-438734848), [__3__](https://github.com/sindresorhus/awesome/pull/1811#pullrequestreview-438736118), [__4__](https://github.com/sindresorhus/awesome/pull/1804#pullrequestreview-438821530) 2. The list over 30-days old, has over 150 stars 3. I [__explained here__](https://github.com/mhxion/awesome-discord-communities/blob/main/FAQ.md#why-does-not-this-list-follow-convential-awesome-list-framework) why I'd used `Notable Channels` and [badges](https://github.com/mhxion/awesome-discord-communities/blob/main/badges.md) instead a description for each entry. 4. Only [table-pipe-alignment](https://github.com/remarkjs/remark-lint/tree/main/packages/remark-lint-table-pipe-alignment) markdown lint rule was ignored because as the rule has mentioned, it was impossible to adapt the cell with variable number of images without making the code too messy. 5. I added this under _Gaming_ due to Discord being [more known for that](https://www.howtogeek.com/660601/is-discord-right-for-your-business/). **https://github.com/mhxion/awesome-discord-communities#readme** **Over the years hundreds of developer communities have made [Discord](discord.com/) their home for helping newcomers in tech, collaborating with open-source project users, and actively contributing by creating occasional programming challenges; this list aggregates the best of them. While existing helper-platforms like Stack Overflow, forums do their job well, they cannot be used for interacting live (debugging), Discord communities fill this major gap. The developer-friendlier the communities, the more productive collaboration is. As of now this list holds over 200 of them (and growing), each of them had gone through proper [review policy](https://github.com/mhxion/awesome-discord-communities/blob/main/CONTRIBUTING.md#review-policy), and other safety requirements, each carrying useful [links](https://github.com/mhxion/awesome-discord-communities/blob/main/badges.md); no other awesome Discord list exists to this extend until now. By nature this list is correlated with [awesome-slack](https://github.com/filipelinhares/awesome-slack#readme).** ### By submitting this pull request I confirm I've read and complied with the below requirements 🖖 **Please read it multiple times. I spent a lot of time on these guidelines and most people miss a lot.** ## Requirements for your pull request - **Don't waste my time.** Do a good job, adhere to all the guidelines, and be responsive. - **You have to review at least 2 other [open pull requests](https://github.com/sindresorhus/awesome/pulls?q=is%3Apr+is%3Aopen).** Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. **Just commenting “looks good” or simply marking the pull request as approved does not count!** You have to actually point out mistakes or improvement suggestions. - You have read and understood the [instructions for creating a list](create-list.md). - This pull request has a title in the format `Add Name of List`. - ✅ `Add Swift` - ✅ `Add Software Architecture` - ❌ `Update readme.md` - ❌ `Add Awesome Swift` - ❌ `Add swift` - ❌ `Adding Swift` - ❌ `Added Swift` - Your entry here should include a short description about the project/theme of the list. **It should not describe the list itself.** The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. - ✅ `- [iOS](…) - Mobile operating system for Apple phones and tablets.` - ✅ `- [Framer](…) - Prototyping interactive UI designs.` - ❌ `- [iOS](…) - Resources and tools for iOS development.` - ❌ `- [Framer](…)` - ❌ `- [Framer](…) - prototyping interactive UI designs` - Your entry should be added at the bottom of the appropriate category. - The suggested Awesome list complies with the below requirements. ## Requirements for your Awesome list - **Has been around for at least 30 days.**<br>That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent. - Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. - Run [`awesome-lint`](https://github.com/sindresorhus/awesome-lint) on your list and fix the reported issues. If there are false-positives or things that cannot/shouldn't be fixed, please [report it](https://github.com/sindresorhus/awesome-lint/issues/new). - The default branch should be named [`main`, not `master`](https://www.zdnet.com/article/github-to-replace-master-with-alternative-term-to-avoid-slavery-references/). - **Includes a succinct description of the project/theme at the top of the readme.** [(Example)](https://github.com/willempienaar/awesome-quantified-self) - ✅ `Mobile operating system for Apple phones and tablets.` - ✅ `Prototyping interactive UI designs.` - ❌ `Resources and tools for iOS development.` - ❌ `Awesome Framer packages and tools.` - It's the result of hard work and the best I could possibly produce. **If you have not put in considerable effort into your list, your pull request will be immediately closed.** - The repo name of your list should be in lowercase slug format: `awesome-name-of-list`. - ✅ `awesome-swift` - ✅ `awesome-web-typography` - ❌ `awesome-Swift` - ❌ `AwesomeWebTypography` - The heading title of your list should be in [title case](https://capitalizemytitle.com/) format: `# Awesome Name of List`. - ✅ `# Awesome Swift` - ✅ `# Awesome Web Typography` - ❌ `# awesome-swift` - ❌ `# AwesomeSwift` - Non-generated Markdown file in a GitHub repo. - The repo should have `awesome-list` & `awesome` as [GitHub topics](https://help.github.com/articles/about-topics). I encourage you to add more relevant topics. - Not a duplicate. Please search for existing submissions. - Only has awesome items. Awesome lists are curations of the best, not everything. - Does not contain items that are unmaintained, has archived repo, deprecated, or missing docs. If you really need to include such items, they should be in a separate Markdown file. - Includes a project logo/illustration whenever possible. - Either centered, fullwidth, or placed at the top-right of the readme. [(Example)](https://github.com/sindresorhus/awesome-electron) - The image should link to the project website or any relevant website. - **The image should be high-DPI.** Set it to maximum half the width of the original image. - Entries have a description, unless the title is descriptive enough by itself. It rarely is though. - Includes the [Awesome badge](awesome.md#awesome-badge). - Should be placed on the right side of the readme heading. - Can be placed centered if the list has a centered graphics header. - Should link back to this list. - Has a Table of Contents section. - Should be named `Contents`, not `Table of Contents`. - Should be the first section in the list. - Should only have one level of [nested lists](https://commonmark.org/help/tutorial/10-nestedLists.html), preferably none. - Has an appropriate license. - **We strongly recommend the [CC0 license](https://creativecommons.org/publicdomain/zero/1.0/), but any [Creative Commons license](https://creativecommons.org/choose/) will work.** - Tip: You can quickly add it to your repo by going to this URL: `https://github.com/<user>/<repo>/community/license/new?branch=master&template=cc0-1.0` (replace `<user>` and `<repo>` accordingly). - A code license like MIT, BSD, Apache, GPL, etc, is not acceptable. Neither are WTFPL and [Unlicense](https://unlicense.org). - Place a file named `license` or `LICENSE` in the repo root with the license text. - **Do not** add the license name or text to the readme. GitHub already shows the license name at the top of the repo. - To verify that you've read all the guidelines, please comment on your pull request with just the word `unicorn`. - Has [contribution guidelines](awesome.md#include-contribution-guidelines). - The file should be named `contributing.md`. Casing is up to you. - Has consistent formatting and proper spelling/grammar. - The link and description are separated by a dash. <br>Example: `- [AVA](…) - JavaScript test runner.` - The description starts with an uppercase character and ends with a period. - Consistent and correct naming. For example, `Node.js`, not `NodeJS` or `node.js`. - Doesn't include a Travis badge.<br>You can still use Travis for list linting, but the badge has no value in the readme. - Doesn't include an `Inspired by awesome-foo` or `Inspired by the Awesome project` kinda link at the top of the readme. The Awesome badge is enough. **Go to the top and read it again.** --- _{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

GiteaMirror added the pull-request label 2025-11-06 16:02:05 -06:00

GiteaMirror closed this issue 2025-11-06 16:02:05 -06:00

GiteaMirror referenced this issue 2025-11-06 16:03:07 -06:00

[PR #1866] [MERGED] Add TALL Stack #1912

GiteaMirror referenced this issue 2025-11-06 16:03:10 -06:00

[PR #1868] [MERGED] Add YouTubers #1914

GiteaMirror referenced this issue 2026-04-15 11:47:03 -05:00

[PR #1866] [MERGED] Add TALL Stack #4517

GiteaMirror referenced this issue 2026-04-15 11:47:07 -05:00

[PR #1868] [MERGED] Add YouTubers #4519

GiteaMirror referenced this issue 2026-04-17 11:56:44 -05:00

[PR #1866] [MERGED] Add TALL Stack #7277

GiteaMirror referenced this issue 2026-04-17 11:56:47 -05:00

[PR #1868] [MERGED] Add YouTubers #7279

GiteaMirror referenced this issue 2026-04-19 04:12:21 -05:00

[PR #1866] [MERGED] Add TALL Stack #10038

GiteaMirror referenced this issue 2026-04-19 04:12:26 -05:00

[PR #1868] [MERGED] Add YouTubers #10040

GiteaMirror referenced this issue 2026-04-21 15:15:05 -05:00

[PR #1866] [MERGED] Add TALL Stack #12802

GiteaMirror referenced this issue 2026-04-21 15:15:08 -05:00

[PR #1868] [MERGED] Add YouTubers #12804

GiteaMirror referenced this issue 2026-04-24 10:59:32 -05:00

[PR #1866] [MERGED] Add TALL Stack #15203

GiteaMirror referenced this issue 2026-04-24 10:59:37 -05:00

[PR #1868] [MERGED] Add YouTubers #15205

GiteaMirror referenced this issue 2026-05-02 15:34:22 -05:00

[PR #1866] [MERGED] Add TALL Stack #17558

GiteaMirror referenced this issue 2026-05-02 15:34:25 -05:00

[PR #1868] [MERGED] Add YouTubers #17560

GiteaMirror referenced this issue 2026-05-07 22:55:26 -05:00

[PR #1866] [MERGED] Add TALL Stack #20293

GiteaMirror referenced this issue 2026-05-07 22:55:47 -05:00

[PR #1868] [MERGED] Add YouTubers #20295

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

gh-pages

No results found.

Labels

Clear labels

enhancement

help wanted

invalid

list request

pull-request

Mirrored from GitHub Pull Request

question

No Label pull-request

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

GiteaMirror ninjasurge

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-sindresorhus#1866