github-starred/awesome-sindresorhus
2
0
Fork 0
mirror of https://github.com/sindresorhus/awesome.git synced 2026-03-12 10:46:16 -05:00
Code Issues 51 Packages Projects Releases Wiki Activity

[PR #1054] [CLOSED] Add Mithril #1270

New Issue
Closed
opened 2025-11-06 15:36:24 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-06 15:36:24 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/sindresorhus/awesome/pull/1054
Author: @orbitbot
Created: 9/19/2017
Status: ❌ Closed

Base: master ← Head: patch-2

📝 Commits (10+)

📊 Changes

5 files changed (+69 additions, -14 deletions)

View changed files

📝 awesome.md (+32 -6)
➕ media/mentioned-badge.sketch (+0 -0)
➕ media/mentioned-badge.svg (+1 -0)
📝 pull_request_template.md (+3 -2)
📝 readme.md (+33 -6)

📄 Description

https://github.com/orbitbot/awesome-mithril

The awesome Mithril list covers links, guides, tools and templates to use with the Mithril.js frontend framework, and is collecting more over time by the Mithril community.

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.
      • 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.
      • 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.
      • 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/1054 **Author:** [@orbitbot](https://github.com/orbitbot) **Created:** 9/19/2017 **Status:** ❌ Closed **Base:** `master` ← **Head:** `patch-2` --- ### 📝 Commits (10+) - [`9838ee4`](https://github.com/sindresorhus/awesome/commit/9838ee4baf06898684d74ae915456639be4d2b79) Add Mithril.js to Front-End Development section - [`5088200`](https://github.com/sindresorhus/awesome/commit/5088200957eb7f720090d98ac32a71c6262c7bd6) Fix link for AS3 language (#1060) - [`be783ed`](https://github.com/sindresorhus/awesome/commit/be783eda3cac0c1c22bcbac9ba61e2d9e4f35bb5) Crypto Currency Tools & Algorithms (#1033) - [`702ee67`](https://github.com/sindresorhus/awesome/commit/702ee6783e19a4a8e8b0d0d87e3e2fac45a21e2c) Guideline clarifications - [`c5ec0bc`](https://github.com/sindresorhus/awesome/commit/c5ec0bcceb99312d6c2ffa6647e24a8ea126ae61) Core ML Models (#1046) - [`fe9032d`](https://github.com/sindresorhus/awesome/commit/fe9032da4ae1b7b40043ff31dd3a150f013fc7d4) Add GNOME (#1025) - [`b017e5e`](https://github.com/sindresorhus/awesome/commit/b017e5e732e47283efb4f625466e95f43421ba84) Fix spelling (#1077) - [`6b8d5bc`](https://github.com/sindresorhus/awesome/commit/6b8d5bce7588c7ca7c07f2cc42d11617717422ca) Minor grammar enhancements to awesome.md (#1081) - [`9f83a94`](https://github.com/sindresorhus/awesome/commit/9f83a94bbc20b33f054c2b48e8ad547f9de143eb) Try out CodeSponsor - [`de62988`](https://github.com/sindresorhus/awesome/commit/de629886d66d2a7e57292568017f69a39223a4a1) Add Deep Learning Education (#954) ### 📊 Changes **5 files changed** (+69 additions, -14 deletions) <details> <summary>View changed files</summary> 📝 `awesome.md` (+32 -6) ➕ `media/mentioned-badge.sketch` (+0 -0) ➕ `media/mentioned-badge.svg` (+1 -0) 📝 `pull_request_template.md` (+3 -2) 📝 `readme.md` (+33 -6) </details> ### 📄 Description <!-- Congrats on creating an Awesome list! 🎉 --> <!-- Please fill in the below placeholders --> https://github.com/orbitbot/awesome-mithril The awesome Mithril list covers links, guides, tools and templates to use with the Mithril.js frontend framework, and is collecting more over time by the Mithril community. # 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.<br>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.**<br>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.**<br>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. - 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.** - 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. - Each link description starts with an uppercase character and ends with a period.<br>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.<br>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. --- <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 15:36:24 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
enhancement
help wanted
invalid
list request
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-sindresorhus#1270
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?