This pull request has a descriptive title. For example, Add Name of List, not Update readme.md or Add awesome list.
The entry in the Awesome list should:
Include a short description about the project/theme of the list. It should not describe the list itself. Example: - [Fish](…) - User-friendly shell., not - [Fish](…) - Resources for Fish..
Be added at the bottom of the appropriate category.
The list I'm submitting complies with these requirements:
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.
It's the result of hard work and the best I could possibly produce.
Non-generated Markdown file in a GitHub repo.
Includes a succinct description of the project/theme at the top of the readme.(Example)
The repo should have awesome-list & awesome as GitHub topics. I encourage you to add more relevant topics.
Not a duplicate.
Only has awesome items. Awesome lists are curations of the best, not everything.
Includes a project logo/illustration whenever possible.
The file should be named contributing.md. Casing is up to you.
Has consistent formatting and proper spelling/grammar.
Each link description starts with an uppercase character and ends with a period. Example: - [AVA](…) - JavaScript test runner.
Drop all the A / An prefixes in the descriptions.
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.
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/1012
**Author:** [@fabacab](https://github.com/fabacab)
**Created:** 7/19/2017
**Status:** ✅ Merged
**Merged:** 7/22/2017
**Merged by:** [@sindresorhus](https://github.com/sindresorhus)
**Base:** `master` ← **Head:** `lockpicking`
---
### 📝 Commits (2)
- [`9196e89`](https://github.com/sindresorhus/awesome/commit/9196e89d21c556524a77da16c374d48b573d623d) Propose inclusion of Awesome Lockpicking list.
- [`2c28eb7`](https://github.com/sindresorhus/awesome/commit/2c28eb70956cd00dd4ad4776f8d2eaa9b8112df6) Add description to Lockpicking list.
### 📊 Changes
**1 file changed** (+1 additions, -0 deletions)
<details>
<summary>View changed files</summary>
📝 `readme.md` (+1 -0)
</details>
### 📄 Description
**https://github.com/meitar/awesome-lockpicking**
**A curated list of awesome guides, tools, and other resources related to the security and compromise of locks, safes, and keys.**
# 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.**
- [x] I have read and understood the [contribution guidelines](https://github.com/sindresorhus/awesome/blob/master/contributing.md) and the [instructions for creating a list](https://github.com/sindresorhus/awesome/blob/master/create-list.md).
- [x] This pull request has a descriptive title.<br>For example, `Add Name of List`, not `Update readme.md` or `Add awesome list`.
- [x] The entry in the Awesome list should:
- [ ] Include a short description about the project/theme of the list. **It should not describe the list itself.**<br>Example: `- [Fish](…) - User-friendly shell.`, not `- [Fish](…) - Resources for Fish.`.
- [x] Be added at the bottom of the appropriate category.
- [x] The list I'm submitting complies with these requirements:
- [x] **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.
- [x] It's the result of hard work and the best I could possibly produce.
- [x] Non-generated Markdown file in a GitHub repo.
- [x] **Includes a succinct description of the project/theme at the top of the readme.** [(Example)](https://github.com/willempienaar/awesome-quantified-self)
- [x] 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.
- [x] Not a duplicate.
- [x] Only has awesome items. Awesome lists are curations of the best, not everything.
- [ ] Includes a project logo/illustration whenever possible.
- 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.
- [x] Entries have a description, unless the title is descriptive enough by itself. It rarely is though.
- [x] Has the [Awesome badge](https://github.com/sindresorhus/awesome/blob/master/awesome.md#awesome-badge) on the right side of the list heading,
- [x] Has a Table of Contents section.
- [x] Should be named `Contents`, not `Table of Contents`.
- [x] Should be the first section in the list.
- [x] Should only have one level of sub-lists, preferably none.
- [x] Has an [appropriate license](https://github.com/sindresorhus/awesome/blob/master/awesome.md#choose-an-appropriate-license).
- [x] That means something like CC0, **not a code licence like MIT, BSD, Apache, etc.**
- [x] If you use a license badge, it should be SVG, not PNG.
- [x] Has [contribution guidelines](https://github.com/sindresorhus/awesome/blob/master/awesome.md#include-contribution-guidelines).
- [x] The file should be named `contributing.md`. Casing is up to you.
- [x] Has consistent formatting and proper spelling/grammar.
- [x] Each link description starts with an uppercase character and ends with a period.<br>Example: `- [AVA](…) - JavaScript test runner.`
- [x] Drop all the `A` / `An` prefixes in the descriptions.
- [x] Consistent and correct naming. For example, `Node.js`, not `NodeJS` or `node.js`.
- [x] Doesn't include a Travis badge.<br>You can still use Travis for list linting, but the badge has no value in the readme.
- [x] Go to the top and read it again.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/sindresorhus/awesome/pull/1012
Author: @fabacab
Created: 7/19/2017
Status: ✅ Merged
Merged: 7/22/2017
Merged by: @sindresorhus
Base:
master← Head:lockpicking📝 Commits (2)
9196e89Propose inclusion of Awesome Lockpicking list.2c28eb7Add description to Lockpicking list.📊 Changes
1 file changed (+1 additions, -0 deletions)
View changed files
📝
readme.md(+1 -0)📄 Description
https://github.com/meitar/awesome-lockpicking
A curated list of awesome guides, tools, and other resources related to the security and compromise of locks, safes, and keys.
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.
For example,
Add Name of List, notUpdate readme.mdorAdd awesome list.Example:
- [Fish](…) - User-friendly shell., not- [Fish](…) - Resources for Fish..That means 30 days from either the first real commit or when it was open-sourced. Whatever is most recent.
awesome-list&awesomeas 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.A/Anprefixes in the descriptions.Node.js, notNodeJSornode.js.You can still use Travis for list linting, but the badge has no value in the readme.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.