github-starred/awesome-docker
2
0
Fork 0
mirror of https://github.com/veggiemonk/awesome-docker.git synced 2026-03-09 07:25:57 -05:00
Code Issues 5 Packages Projects Releases 1 Wiki Activity

[PR #1187] [MERGED] Modernization (thanks to AI) #1171

New Issue
Closed
opened 2025-11-06 12:16:14 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-06 12:16:14 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/veggiemonk/awesome-docker/pull/1187
Author: @veggiemonk
Created: 10/1/2025
Status: ✅ Merged
Merged: 10/2/2025
Merged by: @veggiemonk

Base: master ← Head: refactor

📝 Commits (5)

📊 Changes

15 files changed (+825 additions, -711 deletions)

View changed files

➕ .github/MAINTENANCE.md (+116 -0)
📝 .github/PULL_REQUEST_TEMPLATE.md (+3 -6)
➕ .github/workflows/broken_links.yml (+134 -0)
➕ .github/workflows/deploy-pages.yml (+51 -0)
➕ .github/workflows/health_report.yml (+84 -0)
📝 .github/workflows/pull_request.yml (+4 -4)
➕ AGENTS.md (+28 -0)
📝 README.md (+5 -8)
📝 package-lock.json (+165 -689)
📝 package.json (+2 -1)
📝 tests/common.mjs (+2 -0)
📝 tests/exclude_in_test.json (+4 -1)
➕ tests/health_check.mjs (+206 -0)
📝 tests/pull_request.mjs (+4 -1)
📝 tests/test_all.mjs (+17 -1)

📄 Description

  • ✅ Removed 3 broken links (labex.io, hashnode.com entries)

  • ✅ Fixed rust-lang.org redirect issue

  • ✅ Added problematic domains to exclusion list (YouTube playlists, aquasec, cloudsmith)

  • ✅ Updated all npm dependencies to latest versions

  • ✅ health_check.mjs - Comprehensive repository health checker

    • Detects archived repositories
    • Identifies stale projects (2+ years inactive)
    • Flags inactive projects (1-2 years)
    • Generates detailed health reports
    • Run with: npm run health-check

  • ✅ test_all.mjs - Now detects archived repositories

    • Added isArchived field to GraphQL query
    • Warns about archived repos that should be marked :skull:
    • Non-blocking warnings (doesn't fail builds)

  • Runs every Monday at 9 AM UTC

  • Checks all 731+ GitHub repositories for health

  • Auto-creates/updates GitHub issue with findings

  • Labels: health-report, maintenance

  • Manual trigger available

  • Runs every Saturday at 2 AM UTC

  • Tests all external links

  • Auto-creates issue when links break

  • Auto-closes issue when all links fixed

  • Labels: broken-links, bug

  • Already checks for duplicates

  • Now also checks for archived repos

  • Validates link format and availability

  • ✅ MAINTENANCE.md - Complete guide for maintainers

    • Monthly, quarterly, and annual tasks
    • Emergency procedures
    • Quality standards
    • Metrics to track

  • ✅ AGENTS.md - Updated with new commands

    • Added health-check command
    • Noted GITHUB_TOKEN requirements
    • Added alphabetical sorting guideline

  • Total Links: 883 (731 GitHub repos + 152 external)

  • Working Links: >99% (after fixes)

  • Abandoned Projects: 15 marked with :skull:

  • Automated Checks: 3 workflows running

  • Automatic detection of abandoned/archived projects

  • Weekly monitoring ensures issues are caught early

  • Proactive alerts via GitHub issues

  • No more manual link checking (automated weekly)

  • Archived repos detected automatically

  • Contributors get instant PR feedback

  • Health metrics tracked over time

  • Clear standards documented

  • Easy onboarding for new maintainers

  • Monday: Health report generated and posted

  • Saturday: Link validation runs

  • Review health report issue

  • Mark any newly archived projects with :skull:

  • Run full health check: npm run health-check

  • Review inactive projects (1-2 years)

  • Consider removing very old abandoned projects

  • Deep cleanup of :skull: projects

  • Update documentation

  • Review categories and organization

  1. Auto-PR for Archived Repos: Bot could auto-create PRs to mark archived repos
  2. Contribution Stats: Track and display top contributors
  3. Category Health: Per-category health metrics
  4. Dependency Updates: Dependabot for npm packages
  5. Star Trending: Track which projects are gaining popularity

  • tests/health_check.mjs - Health checker script

  • .github/workflows/health_report.yml - Weekly health workflow

  • .github/workflows/broken_links.yml - Link validation workflow

  • .github/MAINTENANCE.md - Maintainer guide

  • AGENTS.md - AI agent guidelines

  • README.md - Removed 3 broken links, fixed 1 redirect

  • tests/test_all.mjs - Added archive detection

  • tests/exclude_in_test.json - Added problematic domains

  • package.json - Added health-check script

  • package-lock.json - Updated dependencies

Before: Manual maintenance, broken links accumulate, outdated projects linger
After: Automated health monitoring, proactive issue detection, systematic maintenance

The list is now self-maintaining with minimal human oversight required.

Generated: 2025-10-01

Quality Standards

Note that we can help you achieve those standards, just try your best and be brave.
We'll guide you to the best of our abilities.

To be on the list, it would be nice if entries adhere to these quality standards:

  • It should take less than 20 sec to find what is the project, how to install it and how to use it.
  • Generally useful to the community.
  • A project on GitHub with a well documented README.md file and plenty of examples is considered high quality.
  • Clearly stating if an entry is related to (Linux) containers and not to Docker. There is an awesome list for that.
  • Clearly stating "what is it" i.e. which category it belongs to.
  • Clearly stating "what is it for" i.e. mention a real problem it solves (even a small one). Make it clear for the next person.
  • If it is a WIP (work in progress, not safe for production), please mention it. (Remember the time before Docker 1.0 ? ;-) )
  • Always put the link to the GitHub project instead of the website!

To be on the list, the project must have:

  • How to setup/install the project
  • How to use the project (examples)

If your PR is not merged, we will tell you why so that you may be able to improve it.
But usually, we are pretty relaxed people, so just come and say hi, we'll figure something out together.

Rules for Pull Request

  • Each item should be limited to one link, no duplicates, no redirection (careful with http vs https!)
  • The link should be the name of the package or project or website
  • Description should be clear and concise (read it out loud to be sure)
  • Description should follow the link, on the same line
  • Entries are listed alphabetically, please respect the order
  • If you want to add more than one link, please don't do all PR on the exact same line, it usually results in conflicts and your PR cannot be automatically merged...

Please contribute links to packages/projects you have used or are familiar with. This will help ensure high-quality entries.

Your commit message will be a tweet so write a good commit message, keep that in mind :)

🔄 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/veggiemonk/awesome-docker/pull/1187 **Author:** [@veggiemonk](https://github.com/veggiemonk) **Created:** 10/1/2025 **Status:** ✅ Merged **Merged:** 10/2/2025 **Merged by:** [@veggiemonk](https://github.com/veggiemonk) **Base:** `master` ← **Head:** `refactor` --- ### 📝 Commits (5) - [`c30ce6a`](https://github.com/veggiemonk/awesome-docker/commit/c30ce6a693f2c7918259b8a9b2eda3d562076ca2) - ✅ Removed 3 broken links (labex.io, hashnode.com entries) - [`155a2d4`](https://github.com/veggiemonk/awesome-docker/commit/155a2d4023bc3d1d7bfaba96d16c145dfc3e4a40) update github actions - [`ed3f563`](https://github.com/veggiemonk/awesome-docker/commit/ed3f563a12c5b238314f74f8e4c23acdf0acd73b) remove dead links - [`edfd7d6`](https://github.com/veggiemonk/awesome-docker/commit/edfd7d6f43c9cd1ae896c7bbdaf73ce475acec08) set timeout - [`6f649c5`](https://github.com/veggiemonk/awesome-docker/commit/6f649c5c169a40beab217179d60e4997a3225f89) Add badges ### 📊 Changes **15 files changed** (+825 additions, -711 deletions) <details> <summary>View changed files</summary> ➕ `.github/MAINTENANCE.md` (+116 -0) 📝 `.github/PULL_REQUEST_TEMPLATE.md` (+3 -6) ➕ `.github/workflows/broken_links.yml` (+134 -0) ➕ `.github/workflows/deploy-pages.yml` (+51 -0) ➕ `.github/workflows/health_report.yml` (+84 -0) 📝 `.github/workflows/pull_request.yml` (+4 -4) ➕ `AGENTS.md` (+28 -0) 📝 `README.md` (+5 -8) 📝 `package-lock.json` (+165 -689) 📝 `package.json` (+2 -1) 📝 `tests/common.mjs` (+2 -0) 📝 `tests/exclude_in_test.json` (+4 -1) ➕ `tests/health_check.mjs` (+206 -0) 📝 `tests/pull_request.mjs` (+4 -1) 📝 `tests/test_all.mjs` (+17 -1) </details> ### 📄 Description - ✅ Removed 3 broken links (labex.io, hashnode.com entries) - ✅ Fixed rust-lang.org redirect issue - ✅ Added problematic domains to exclusion list (YouTube playlists, aquasec, cloudsmith) - ✅ Updated all npm dependencies to latest versions - ✅ **health_check.mjs** - Comprehensive repository health checker - Detects archived repositories - Identifies stale projects (2+ years inactive) - Flags inactive projects (1-2 years) - Generates detailed health reports - Run with: `npm run health-check` - ✅ **test_all.mjs** - Now detects archived repositories - Added `isArchived` field to GraphQL query - Warns about archived repos that should be marked `:skull:` - Non-blocking warnings (doesn't fail builds) - Runs every Monday at 9 AM UTC - Checks all 731+ GitHub repositories for health - Auto-creates/updates GitHub issue with findings - Labels: `health-report`, `maintenance` - Manual trigger available - Runs every Saturday at 2 AM UTC - Tests all external links - Auto-creates issue when links break - Auto-closes issue when all links fixed - Labels: `broken-links`, `bug` - Already checks for duplicates - Now also checks for archived repos - Validates link format and availability - ✅ **MAINTENANCE.md** - Complete guide for maintainers - Monthly, quarterly, and annual tasks - Emergency procedures - Quality standards - Metrics to track - ✅ **AGENTS.md** - Updated with new commands - Added health-check command - Noted GITHUB_TOKEN requirements - Added alphabetical sorting guideline - **Total Links**: 883 (731 GitHub repos + 152 external) - **Working Links**: >99% (after fixes) - **Abandoned Projects**: 15 marked with `:skull:` - **Automated Checks**: 3 workflows running - **Automatic detection** of abandoned/archived projects - **Weekly monitoring** ensures issues are caught early - **Proactive alerts** via GitHub issues - No more manual link checking (automated weekly) - Archived repos detected automatically - Contributors get instant PR feedback - Health metrics tracked over time - Clear standards documented - Easy onboarding for new maintainers - Monday: Health report generated and posted - Saturday: Link validation runs - Review health report issue - Mark any newly archived projects with `:skull:` - Run full health check: `npm run health-check` - Review inactive projects (1-2 years) - Consider removing very old abandoned projects - Deep cleanup of `:skull:` projects - Update documentation - Review categories and organization 1. **Auto-PR for Archived Repos**: Bot could auto-create PRs to mark archived repos 2. **Contribution Stats**: Track and display top contributors 3. **Category Health**: Per-category health metrics 4. **Dependency Updates**: Dependabot for npm packages 5. **Star Trending**: Track which projects are gaining popularity - `tests/health_check.mjs` - Health checker script - `.github/workflows/health_report.yml` - Weekly health workflow - `.github/workflows/broken_links.yml` - Link validation workflow - `.github/MAINTENANCE.md` - Maintainer guide - `AGENTS.md` - AI agent guidelines - `README.md` - Removed 3 broken links, fixed 1 redirect - `tests/test_all.mjs` - Added archive detection - `tests/exclude_in_test.json` - Added problematic domains - `package.json` - Added health-check script - `package-lock.json` - Updated dependencies Before: Manual maintenance, broken links accumulate, outdated projects linger After: **Automated health monitoring, proactive issue detection, systematic maintenance** The list is now **self-maintaining** with minimal human oversight required. --- *Generated: 2025-10-01* <!-- Congrats on creating an Awesome Docker entry! 🎉 --> <!-- **Remember that entries are ordered alphabetically** --> <!-- TLDR: * all entries sorted alphabetically, * If paying service add :heavy_dollar_sign: * If WIP add :construction: * clear and short description of the project * project MUST have: How to setup/install * project MUST have: How to use (examples) * we can help you get there :) --> # Quality Standards Note that we can help you achieve those standards, just try your best and be brave. We'll guide you to the best of our abilities. To be on the list, it would be **nice** if entries adhere to these quality standards: - It should take less than 20 sec to find what is the project, how to install it and how to use it. - Generally useful to the community. - A project on GitHub with a well documented `README.md` file and plenty of examples is considered high quality. - Clearly stating if an entry is related to (Linux) containers and not to Docker. There is an [awesome list](https://github.com/Friz-zy/awesome-linux-containers) for that. - Clearly stating "what is it" i.e. which category it belongs to. - Clearly stating "what is it for" i.e. mention a real problem it solves (even a small one). Make it clear for the next person. - If it is a **WIP** (work in progress, not safe for production), please mention it. (Remember the time before Docker 1.0 ? ;-) ) - Always put the link to the GitHub project instead of the website! To be on the list, the project **must** have: - How to setup/install the project - How to use the project (examples) If your PR is not merged, we will tell you why so that you may be able to improve it. But usually, we are pretty relaxed people, so just come and say hi, we'll figure something out together. # Rules for Pull Request - Each item should be limited to one link, no duplicates, no redirection (careful with `http` vs `https`!) - The link should be the name of the package or project or website - Description should be clear and concise (read it out loud to be sure) - Description should follow the link, on the same line - Entries are listed alphabetically, please respect the order - If you want to add more than one link, please don't do all PR on the exact same line, it usually results in conflicts and your PR cannot be automatically merged... Please contribute links to packages/projects you have used or are familiar with. This will help ensure high-quality entries. #### Your commit message will be a [tweet](https://twitter.com/awesome_docker) so write a [good commit message](https://chris.beams.io/posts/git-commit/), keep that in mind :) --- <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 12:16:14 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
broken-links
bug
cannot be evaluated
enhancement
health-report
help wanted
maintenance
pending-evaluation
pull-request
Mirrored from GitHub Pull Request
 question
team discussion
weekly-digest
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-docker#1171
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?