github-starred/awesome-sindresorhus
2
0
Fork 0
mirror of https://github.com/sindresorhus/awesome.git synced 2026-05-07 12:34:47 -05:00
Code Issues 388 Packages Projects Releases Wiki Activity

[PR #1336] [CLOSED] Add Database Tools #4104

New Issue
Closed
opened 2026-04-15 11:33:37 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-15 11:33:37 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/sindresorhus/awesome/pull/1336
Author: @mgramin
Created: 6/17/2018
Status: ❌ Closed

Base: master ← Head: master

📝 Commits (9)

📊 Changes

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

View changed files

📝 readme.md (+1 -0)

📄 Description

https://github.com/mgramin/awesome-db-tools

This is a community driven list of database tools (ide, cli, managing, monitoring, migrations, modellers, visualization etc)

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/1336 **Author:** [@mgramin](https://github.com/mgramin) **Created:** 6/17/2018 **Status:** ❌ Closed **Base:** `master` ← **Head:** `master` --- ### 📝 Commits (9) - [`4655294`](https://github.com/sindresorhus/awesome/commit/4655294583527429b042843e09c4a2823c0fe253) Add awesome-db-tools - [`2843323`](https://github.com/sindresorhus/awesome/commit/28433230bc1f349c48997daa111b16ca17ce6a31) Add awesome-db-tools - [`aa20471`](https://github.com/sindresorhus/awesome/commit/aa2047156a2c77395f4c9f0c15eecc1944ed1a50) Merge branch 'master' of https://github.com/sindresorhus/awesome - [`836c0ad`](https://github.com/sindresorhus/awesome/commit/836c0ad723328fc940e9e9ccb3f29c48b37a28a0) Update name - [`90bc7b7`](https://github.com/sindresorhus/awesome/commit/90bc7b748ce8b7b47a0f56f8a6fe5ca1c1469bd0) Fix ordering - [`f244f64`](https://github.com/sindresorhus/awesome/commit/f244f6428526798573c8673bbc03f101c096078a) Update readme.md - [`4b8af20`](https://github.com/sindresorhus/awesome/commit/4b8af20c25e9a2dcdf8f5bb38c33edc440d4a02d) Update readme.md - [`cae619b`](https://github.com/sindresorhus/awesome/commit/cae619ba1302165ca4c6dfddb961a236dd6d53c3) Update readme.md - [`f7d4c11`](https://github.com/sindresorhus/awesome/commit/f7d4c1198e1df08b1aa3813e2be07b8a3d2a296b) Update readme.md ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `readme.md` (+1 -0) </details> ### 📄 Description <!-- Congrats on creating an Awesome list! 🎉 --> <!-- Please fill in the below placeholders --> https://github.com/mgramin/awesome-db-tools This is a community driven list of database tools (ide, cli, managing, monitoring, migrations, modellers, visualization etc) ### 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.<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: ## Requirements for your Awesome list - **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. - 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. <br>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.<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 2026-04-15 11:33:37 -05: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#4104
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?