Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add to sindresorhus/awesome #32

Closed
25 tasks done
eric-hc opened this issue Mar 6, 2023 · 4 comments
Closed
25 tasks done

Add to sindresorhus/awesome #32

eric-hc opened this issue Mar 6, 2023 · 4 comments

Comments

@eric-hc
Copy link
Contributor

eric-hc commented Mar 6, 2023

Add awesome-orgs to https://github.com/sindresorhus/awesome

Per requirements:

  • At least 30 days (initial commit 47095ab)
  • You have to review at least 2 other open pull requests.
  • Run awesome-lint on your list and fix the reported issues.
  • The default branch should be named main, not master.
  • Includes a succinct description of the project/theme at the top of the readme.
  • It's the result of hard work and the best I could possibly produce.
  • The repo name of your list should be in lowercase slug format: awesome-name-of-list.
  • The heading title of your list should be in title case format: # Awesome Name of List.
  • The repo should have awesome-list & awesome as GitHub topics.
  • Non-generated Markdown file in a GitHub repo.
  • 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.
  • 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.
  • Has an appropriate license.
  • Has contribution guidelines.
  • All non-important but necessary content (like extra copyright notices, hyperlinks to sources, pointers to expansive content, etc) should be grouped in a Footnotes section at the bottom of the readme. The section should not be present in the Table of Contents.
  • Has consistent formatting and proper spelling/grammar.
  • Does not use hard-wrapping.
  • Does not include a CI (e.g. GitHub Actions) badge.
  • Does not 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.
@swand0g
Copy link
Contributor

swand0g commented Mar 23, 2023

sindresorhus/awesome#2560

@swand0g swand0g pinned this issue Mar 24, 2023
@beansource beansource deleted a comment from Siimarras Mar 26, 2023
@github-actions
Copy link
Contributor

This issue is stale because it has been open 30 days with no activity 🤨 Remove stale label or comment or this will be closed in 5 days 👀

@github-actions github-actions bot added the Stale label Apr 26, 2023
@eric-hc eric-hc removed the Stale label Apr 26, 2023
@swand0g
Copy link
Contributor

swand0g commented Apr 27, 2023

:(

@eric-hc
Copy link
Contributor Author

eric-hc commented Feb 27, 2024

This request has been officially denied.

@eric-hc eric-hc closed this as not planned Won't fix, can't repro, duplicate, stale Feb 27, 2024
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

No branches or pull requests

2 participants