[PR #3354] [CLOSED] Add Meshery to Development Environment #39669

New Issue

GiteaMirror · 2026-06-04T08:42:04-05:00

GiteaMirror commented

2026-06-04 08:42:04 -05:00

📋 Pull Request Information

Original PR: https://github.com/sindresorhus/awesome/pull/3354
Author: @Denish3436
Created: 2/8/2025
Status: ❌ Closed

Base: main ← Head: add-meshery-kanvas

📝 Commits (2)

daf5a63 Add meshery and kanvas
3ded2e1 Add Meshery to Development Environment section

📊 Changes

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

View changed files

📝 readme.md (+1 -0)

📄 Description

[https://github.com/meshery/meshery]

This pull request adds one new entry to the Development Environment section:

Meshery (Open Source) - Open-source cloud-native manager for designing and managing Kubernetes-based infrastructure and applications. Meshery offers visual, collaborative GitOps and multi-cluster management.

Meshery is a robust solution that empowers developers and DevOps teams by simplifying complex Kubernetes operations and enhancing infrastructure management. Its inclusion enriches the resource pool for users seeking modern, cloud-native development environment tools.

By submitting this pull request I confirm I've read and complied with the below requirements 🖖

Requirements for your pull request

Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. Instead use #2242 for incubation visibility.
Don't waste my time. Do a good job, adhere to all the guidelines, and be responsive.
You have to review at least 2 other open pull requests.
Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. Just commenting “looks good” or simply marking the pull request as approved does not count! You have to actually point out mistakes or improvement suggestions. Comments pointing out lint violation are allowed, but does not count as a review.
You have read and understood the instructions for creating a list.
This pull request has a title in the format Add Name of List. It should not contain the word Awesome.
- ✅ Add Swift
- ✅ Add Software Architecture
- ❌ Update readme.md
- ❌ Add Awesome Swift
- ❌ Add swift
- ❌ add Swift
- ❌ Adding Swift
- ❌ Added Swift
Your entry here should include a short description of the project/theme of the list. It should not describe the list itself. The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. It should not contain the name of the list.
- ✅ - [iOS](…) - Mobile operating system for Apple phones and tablets.
- ✅ - [Framer](…) - Prototyping interactive UI designs.
- ❌ - [iOS](…) - Resources and tools for iOS development.
- ❌ - [Framer](…)
- ❌ - [Framer](…) - prototyping interactive UI designs
Your entry should be added at the bottom of the appropriate category.
The title of your entry should be title-cased and the URL to your list should end in #readme.
- Example: - [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.
No blockchain-related lists.
The suggested Awesome list complies with the below requirements.

unicorn

_{🔄 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/3354 **Author:** [@Denish3436](https://github.com/Denish3436) **Created:** 2/8/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `add-meshery-kanvas` --- ### 📝 Commits (2) - [`daf5a63`](https://github.com/sindresorhus/awesome/commit/daf5a63cc2a2742383511ab44523edf364ff4db7) Add meshery and kanvas - [`3ded2e1`](https://github.com/sindresorhus/awesome/commit/3ded2e1974512842be21ad814a4ee84eb8ef342c) Add Meshery to Development Environment section ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `readme.md` (+1 -0) </details> ### 📄 Description **[https://github.com/meshery/meshery]** This pull request adds one new entry to the Development Environment section: - [Meshery](https://github.com/meshery/meshery#readme) (Open Source) - Open-source cloud-native manager for designing and managing Kubernetes-based infrastructure and applications. Meshery offers visual, collaborative GitOps and multi-cluster management. Meshery is a robust solution that empowers developers and DevOps teams by simplifying complex Kubernetes operations and enhancing infrastructure management. Its inclusion enriches the resource pool for users seeking modern, cloud-native development environment tools. ### By submitting this pull request I confirm I've read and complied with the below requirements 🖖 ## Requirements for your pull request - [x] Don't open a Draft / WIP pull request while you work on the guidelines. A pull request should be 100% ready and should adhere to all the guidelines when you open it. **Instead use [#2242](https://github.com/sindresorhus/awesome/issues/2242) for incubation visibility**. - [x] **Don't waste my time.** Do a good job, adhere to all the guidelines, and be responsive. - [x] **You have to review at least 2 other [open pull requests](https://github.com/sindresorhus/awesome/pulls?q=is%3Apr+is%3Aopen).** Try to prioritize unreviewed PRs, but you can also add more comments to reviewed PRs. Go through the below list when reviewing. This requirement is meant to help make the Awesome project self-sustaining. Comment here which PRs you reviewed. You're expected to put a good effort into this and to be thorough. Look at previous PR reviews for inspiration. **Just commenting “looks good” or simply marking the pull request as approved does not count!** You have to actually point out mistakes or improvement suggestions. Comments pointing out lint violation are allowed, but does **not** count as a review. - [x] You have read and understood the [instructions for creating a list](https://github.com/sindresorhus/awesome/blob/main/create-list.md). - [x] This pull request has a title in the format `Add Name of List`. It should not contain the word `Awesome`. - ✅ `Add Swift` - ✅ `Add Software Architecture` - ❌ `Update readme.md` - ❌ `Add Awesome Swift` - ❌ `Add swift` - ❌ `add Swift` - ❌ `Adding Swift` - ❌ `Added Swift` - [x] Your entry here should include a short description of the project/theme of the list. **It should not describe the list itself.** The first character should be uppercase and the description should end in a dot. It should be an objective description and not a tagline or marketing blurb. It should not contain the name of the list. - ✅ `- [iOS](…) - Mobile operating system for Apple phones and tablets.` - ✅ `- [Framer](…) - Prototyping interactive UI designs.` - ❌ `- [iOS](…) - Resources and tools for iOS development.` - ❌ `- [Framer](…)` - ❌ `- [Framer](…) - prototyping interactive UI designs` - [x] Your entry should be added at the bottom of the appropriate category. - [x] The title of your entry should be title-cased and the URL to your list should end in `#readme`. - Example: `- [Software Architecture](https://github.com/simskij/awesome-software-architecture#readme) - The discipline of designing and building software.` - [x] No blockchain-related lists. - [x] The suggested Awesome list complies with the below requirements. unicorn --- <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 2026-06-04 08:42:04 -05:00

GiteaMirror closed this issue

2026-06-04 08:42:06 -05: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#39669