Closed robatwilliams closed 4 years ago
There are some remaining possible issues. If solving them makes the list less useful, I won't solve them.
There have been some updates to the requirements since I opened this issue: https://github.com/sindresorhus/awesome/commits/master/pull_request_template.md
https://github.com/sindresorhus/awesome/commit/e53741c4850efb8117a6ffdf8918399c34bd64b1#diff-081a901bcd6f61bef29110a1bc408818 - in compliance.
https://github.com/sindresorhus/awesome/commit/efc69ed013896c466df6e3ec89f0753eb92edc02#diff-081a901bcd6f61bef29110a1bc408818 - in compliance except:
awesome-lint
on your list and fix the reported issues.https://github.com/sindresorhus/awesome/commit/a4dc681a0a33668ebb0af7f2a4cd89bb0e3318d9#diff-081a901bcd6f61bef29110a1bc408818 - in compliance
sindresorhus/awesome is an extreme mess. Is it really worth putting effort into meeting their guidelines?
Closing; there's little value in full compliance - the list is tidy and organised as it is, and the deviations from requirements are with good reason which add value.
https://github.com/sindresorhus/awesome/blob/master/pull_request_template.md
That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
awesome-list
&awesome
as GitHub topics. I encourage you to add more relevant topics.Contents
, notTable of Contents
.contributing.md
. Casing is up to you.Example:
- [AVA](…) - JavaScript test runner.
Node.js
, notNodeJS
ornode.js
.You can still use Travis for list linting, but the badge has no value in the readme.