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 awesome-computercraft to Awesome meta-list #5

Closed
tomodachi94 opened this issue Sep 4, 2022 · 4 comments
Closed

Add awesome-computercraft to Awesome meta-list #5

tomodachi94 opened this issue Sep 4, 2022 · 4 comments
Assignees

Comments

@tomodachi94
Copy link
Owner

tomodachi94 commented Sep 4, 2022

Tracking issue for getting this list onto sindresorhus/awesome.

@tomodachi94
Copy link
Owner Author

tomodachi94 commented Oct 8, 2022

Here's a checklist of the requirements:

  • Has been around for at least 30 days.
  • 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.
    • This was done automatically when the repository was created.
  • Includes a succinct description of the project/theme at the top of the readme. (Example)
  • 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.
  • The heading title of your list should be in title case format: # Awesome Name of List.
  • 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)
  • Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
  • Includes the Awesome badge.
  • Has a Table of Contents section.
  • Has an appropriate license.
  • Has [contribution guidelines](https://github.com/sindresorhus/awesome/blob/main/awesome.md#include-contribution-guid elines).
  • The file should be named contributing.md. Casing is up to you.
    • It can optionally be linked from the readme in a dedicated section titled Contributing, positioned at the top or bottom of the main content.
      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.
  • The link and description are separated by a dash.
    • Example: - AVA - JavaScript test runner.
    • I'm not sure what to do with this. The literature section follows this, but everything else has a bolded section at the end of the item.
  • 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 use hard-wrapping.
  • Doesn't include a Travis badge.
  • 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.

Super important when the PR gets created:

To verify that you've read all the guidelines, please comment on your pull request with just the word unicorn.

@tomodachi94 tomodachi94 self-assigned this Oct 8, 2022
@tomodachi94
Copy link
Owner Author

PR has been sitting for a few weeks now with no reply.

@tomodachi94
Copy link
Owner Author

See also: sindresorhus/awesome#2405

@tomodachi94
Copy link
Owner Author

PR was merged.

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

1 participant