[PR #1873] [MERGED] Add QR Code #1918

Closed
opened 2025-11-06 16:03:15 -06:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/sindresorhus/awesome/pull/1873
Author: @make-github-pseudonymous-again
Created: 9/29/2020
Status: Merged
Merged: 2/26/2021
Merged by: @sindresorhus

Base: mainHead: main


📝 Commits (7)

  • 4d305b2 Add QR codes.
  • e2024d0 Add #readme to QR codes.
  • af1cfba Fix QR Code title and description.
  • 2b87faf More precision on the capacity of QR codes.
  • fe5c34c Remove duplicated lines.
  • 66d806c Simplify QR Code description
  • 12837b6 Merge remote-tracking branch 'upstream/main'

📊 Changes

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

View changed files

📝 readme.md (+1 -0)

📄 Description

https://github.com/aureooms/awesome-qr-code

This is a curated list of QR code libraries, software and resources. I created it because I could not find any other such list. I have used some of the listed items and even created some.

I have reviewed the following open pull requests: #1816, #1851, #1868, #1869.

Requirements for your pull request

  • You have to review at least 2 other open pull requests.
  • You have read and understood the instructions for creating a list.
  • This pull request has a title in the format Add Name of List.
  • Your entry here should include a short description about the project/theme of the list. It should not describe the list itself.
  • Your entry should be added at the bottom of the appropriate category.

Requirements for your Awesome list

  • Has been around for at least 30 days.
  • 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. (Example)
  • 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.
  • Non-generated Markdown file in a GitHub repo.
  • The repo should have awesome-list & awesome as GitHub 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.
    • 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.
    • 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.
  • 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 use hard-wrapping.
  • 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.

🔄 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/1873 **Author:** [@make-github-pseudonymous-again](https://github.com/make-github-pseudonymous-again) **Created:** 9/29/2020 **Status:** ✅ Merged **Merged:** 2/26/2021 **Merged by:** [@sindresorhus](https://github.com/sindresorhus) **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (7) - [`4d305b2`](https://github.com/sindresorhus/awesome/commit/4d305b2d8d4ad1725e4317d17f451b457efc00a9) Add QR codes. - [`e2024d0`](https://github.com/sindresorhus/awesome/commit/e2024d01e6000969eb377215879463a70c68867f) Add #readme to QR codes. - [`af1cfba`](https://github.com/sindresorhus/awesome/commit/af1cfba1ea6df162f45fcba841af1a831a7bf5f5) Fix QR Code title and description. - [`2b87faf`](https://github.com/sindresorhus/awesome/commit/2b87fafda837ca0bb98f2ef1f2eed1e981151572) More precision on the capacity of QR codes. - [`fe5c34c`](https://github.com/sindresorhus/awesome/commit/fe5c34c19b4d58e73b9beaf80e2e4ab54cfb058f) Remove duplicated lines. - [`66d806c`](https://github.com/sindresorhus/awesome/commit/66d806c628929909263408e8a09d2a2af92b516b) Simplify QR Code description - [`12837b6`](https://github.com/sindresorhus/awesome/commit/12837b608a4c5db42cebe55c629c98fa7acb6b48) Merge remote-tracking branch 'upstream/main' ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `readme.md` (+1 -0) </details> ### 📄 Description **https://github.com/aureooms/awesome-qr-code** **This is a curated list of QR code libraries, software and resources.** I created it because I could not find any other such list. I have used some of the listed items and even created some. I have reviewed [the following open pull requests](https://github.com/sindresorhus/awesome/pulls?q=is%3Apr+reviewed-by%3Aaureooms): #1816, #1851, #1868, #1869. ## Requirements for your pull request - [x] **You have to review at least 2 other [open pull requests](https://github.com/sindresorhus/awesome/pulls?q=is%3Apr+is%3Aopen).** - [x] You have read and understood the [instructions for creating a list](create-list.md). - [x] This pull request has a title in the format `Add Name of List`. - [x] Your entry here should include a short description about the project/theme of the list. **It should not describe the list itself.** - [x] Your entry should be added at the bottom of the appropriate category. ## Requirements for your Awesome list - [x] **Has been around for at least 30 days.** - [x] Run [`awesome-lint`](https://github.com/sindresorhus/awesome-lint) on your list and fix the reported issues. - [x] 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/). - [x] **Includes a succinct description of the project/theme at the top of the readme.** [(Example)](https://github.com/willempienaar/awesome-quantified-self) - [x] It's the result of hard work and the best I could possibly produce. - [x] The repo name of your list should be in lowercase slug format: `awesome-name-of-list`. - [x] The heading title of your list should be in [title case](https://capitalizemytitle.com/) format: `# Awesome Name of List`. - [x] Non-generated Markdown file in a GitHub repo. - [x] The repo should have `awesome-list` & `awesome` as [GitHub topics](https://help.github.com/articles/about-topics). - [x] 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. - [x] Includes a project logo/illustration whenever possible. - [x] Either centered, fullwidth, or placed at the top-right of the readme. [(Example)](https://github.com/sindresorhus/awesome-electron) - [x] The image should link to the project website or any relevant website. - [x] **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] Includes the [Awesome badge](awesome.md#awesome-badge). - [x] Should be placed on the right side of the readme heading. - [x] Should link back to this list. - [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 [nested lists](https://commonmark.org/help/tutorial/10-nestedLists.html), preferably none. - [x] Has an appropriate license. - [x] Place a file named `license` or `LICENSE` in the repo root with the license text. - [x] **Do not** add the license name or text to the readme. GitHub already shows the license name at the top of the repo. - [x] Has [contribution guidelines](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] The link and description are separated by a dash. <br>Example: `- [AVA](…) - JavaScript test runner.` - [x] The description starts with an uppercase character and ends with a period. - [x] Consistent and correct naming. For example, `Node.js`, not `NodeJS` or `node.js`. - [x] Doesn't use [hard-wrapping](https://stackoverflow.com/questions/319925/difference-between-hard-wrap-and-soft-wrap). - [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] 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. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-11-06 16:03:15 -06:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-sindresorhus#1918