[PR #1327] [MERGED] Add CircuitPython #4095

New Issue

GiteaMirror · 2026-04-15T11:33:22-05:00

GiteaMirror commented

2026-04-15 11:33:22 -05:00

📋 Pull Request Information

Original PR: https://github.com/sindresorhus/awesome/pull/1327
Author: @TheKitty
Created: 6/6/2018
Status: ✅ Merged
Merged: 8/3/2018
Merged by: @sindresorhus

Base: master ← Head: patch-2

📝 Commits (3)

a6ce7d5 Add CircuitPython to the Python section
8542f10 Add the #readme
041d1a5 Merge branch 'master' into patch-2

📊 Changes

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

View changed files

📝 readme.md (+1 -0)

📄 Description

Request to add the Adafruit Industries curated awesome list devoted to CircuitPython, a microcontroller based version of Python, to the Python category. The Adafruit CircuitPython awesome list is at https://github.com/adafruit/awesome-circuitpython
[https://github.com/adafruit/awesome-circuitpython]
[Request to add the Adafruit Industries curated awesome list devoted to CircuitPython, a microcontroller based version of Python, to the Python category.]

We have read the guidelines multiple times and have tried to ensure every single item is covered.

[https://github.com/adafruit/awesome-circuitpython]

[Request to add the Adafruit Industries curated awesome list devoted to CircuitPython, a microcontroller based version of Python, to the Python category.]

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.

Requirements for your pull request

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:

Requirements for your Awesome list

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.
- 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/1327 **Author:** [@TheKitty](https://github.com/TheKitty) **Created:** 6/6/2018 **Status:** ✅ Merged **Merged:** 8/3/2018 **Merged by:** [@sindresorhus](https://github.com/sindresorhus) **Base:** `master` ← **Head:** `patch-2` --- ### 📝 Commits (3) - [`a6ce7d5`](https://github.com/sindresorhus/awesome/commit/a6ce7d5cc2c5a14fea7a766ad225d60502b45db3) Add CircuitPython to the Python section - [`8542f10`](https://github.com/sindresorhus/awesome/commit/8542f10b429a71c06309fc1c9996433f8f6a491c) Add the #readme - [`041d1a5`](https://github.com/sindresorhus/awesome/commit/041d1a5a11e7fe73d86434b7f3524e069868e6f5) Merge branch 'master' into patch-2 ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `readme.md` (+1 -0) </details> ### 📄 Description Request to add the Adafruit Industries curated awesome list devoted to CircuitPython, a microcontroller based version of Python, to the Python category. The Adafruit CircuitPython awesome list is at https://github.com/adafruit/awesome-circuitpython [https://github.com/adafruit/awesome-circuitpython] [Request to add the Adafruit Industries curated awesome list devoted to CircuitPython, a microcontroller based version of Python, to the Python category.] We have read the guidelines multiple times and have tried to ensure every single item is covered.   **[https://github.com/adafruit/awesome-circuitpython]** **[Request to add the Adafruit Industries curated awesome list devoted to CircuitPython, a microcontroller based version of Python, to the Python category.]** ### 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.** ## Requirements for your pull request - 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: ## Requirements for your Awesome list - **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. - 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:33:22 -05:00

GiteaMirror closed this issue