[PR #1226] [MERGED] Add Quantum Computing #4014

New Issue

GiteaMirror · 2026-04-15T11:30:55-05:00

GiteaMirror commented

2026-04-15 11:30:55 -05:00

📋 Pull Request Information

Original PR: https://github.com/sindresorhus/awesome/pull/1226
Author: @desireevl
Created: 2/25/2018
Status: ✅ Merged
Merged: 5/30/2019
Merged by: @sindresorhus

Base: master ← Head: master

📝 Commits (7)

114ab3f added quantum computing
cba35eb Merge branch 'master' of https://github.com/sindresorhus/awesome into sindresorhus-master
2f0b21f Merge branch 'sindresorhus-master'
671f240 added description
d6f7f68 Update readme.md
bdc2431 Merge pull request #2 from sindresorhus/master
e2aa077 updated QC description

📊 Changes

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

View changed files

📝 readme.md (+1 -0)

📄 Description

https://github.com/desireevl/awesome-quantum-computing

List on quantum computing resources. QC is a hot topic of interest with wide applications and offers the opportunity to advance fields such as machine learning. As it grows, so does its users who are interested in learning more about it.

The list had a positive response from the community when posted to the quantum sub-Reddit and Facebook group.

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.

I have read and understood the contribution guidelines and the instructions for creating a list.
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.
  - Either 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 sub-lists, preferably none.
- Has an appropriate license.
  - That means something like CC0, not a code licence like MIT, BSD, Apache, etc.
  - WTFPL and Unlicense are not acceptable licenses.
  - If you use a license badge, it should be SVG, not PNG.
- 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.
  - 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/1226 **Author:** [@desireevl](https://github.com/desireevl) **Created:** 2/25/2018 **Status:** ✅ Merged **Merged:** 5/30/2019 **Merged by:** [@sindresorhus](https://github.com/sindresorhus) **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (7) - [`114ab3f`](https://github.com/sindresorhus/awesome/commit/114ab3f03e580722948904eeee1d6494fcb8ffa0) added quantum computing - [`cba35eb`](https://github.com/sindresorhus/awesome/commit/cba35ebf867340e1c91c687d49901a0ec901a589) Merge branch 'master' of https://github.com/sindresorhus/awesome into sindresorhus-master - [`2f0b21f`](https://github.com/sindresorhus/awesome/commit/2f0b21fc3a14232c3e084cce8b182e16889e8e3d) Merge branch 'sindresorhus-master' - [`671f240`](https://github.com/sindresorhus/awesome/commit/671f240191be9a1ff15f3b8f0d62621b691953cc) added description - [`d6f7f68`](https://github.com/sindresorhus/awesome/commit/d6f7f68a78def861da8c7e2503966a7523dadae6) Update readme.md - [`bdc2431`](https://github.com/sindresorhus/awesome/commit/bdc243112bc387ba2a27fabd5e47ed239f28b92f) Merge pull request #2 from sindresorhus/master - [`e2aa077`](https://github.com/sindresorhus/awesome/commit/e2aa0773239a72e437b0c54295f8d9cb70eb76d2) updated QC description ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `readme.md` (+1 -0) </details> ### 📄 Description   **https://github.com/desireevl/awesome-quantum-computing** List on quantum computing resources. QC is a hot topic of interest with wide applications and offers the opportunity to advance fields such as machine learning. As it grows, so does its users who are interested in learning more about it. The list had a positive response from the community when posted to the quantum sub-Reddit and Facebook group. # 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.** - 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). - 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)](https://github.com/willempienaar/awesome-quantified-self) - 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. - Not a duplicate. - Only has awesome items. Awesome lists are curations of the best, not everything. - Includes a project logo/illustration whenever possible. - Either fullwidth or 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. - Entries have a description, unless the title is descriptive enough by itself. It rarely is though. - Includes the [Awesome badge](https://github.com/sindresorhus/awesome/blob/master/awesome.md#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 sub-lists, preferably none. - Has an [appropriate license](https://github.com/sindresorhus/awesome/blob/master/awesome.md#choose-an-appropriate-license). - That means something like CC0, **not a code licence like MIT, BSD, Apache, etc.** - [WTFPL](http://www.wtfpl.net) and [Unlicense](http://unlicense.org) are not acceptable licenses. - If you use a license badge, it should be SVG, not PNG. - Has [contribution guidelines](https://github.com/sindresorhus/awesome/blob/master/awesome.md#include-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. - 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.

GiteaMirror added the pull-request label 2026-04-15 11:30:55 -05:00

GiteaMirror closed this issue