github-starred/awesome-sindresorhus
2
0
Fork 0
mirror of https://github.com/sindresorhus/awesome.git synced 2026-07-19 04:53:11 -05:00
Code Issues 1.7k Packages Projects Releases Wiki Activity

[PR #4130] [CLOSED] Clarify list maintainer responsiveness expectations #21152

New Issue
Closed
opened 2026-05-08 00:18:34 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-05-08 00:18:34 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/sindresorhus/awesome/pull/4130
Author: @zjy-dev
Created: 5/1/2026
Status: ❌ Closed

Base: main ← Head: clarify-maintainer-responsiveness

📝 Commits (1)

  • 7d14273 Clarify maintainer responsiveness expectations

📊 Changes

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

View changed files

📝 create-list.md (+1 -0)

📄 Description

Summary

  • add a short note to the list creation guide that maintainers should review issues and pull requests within a reasonable time
  • suggest asking additional maintainers for help when updates start to pile up

Why

  • addresses #748 by setting expectations for prospective list maintainers before they submit a list
  • keeps the change focused on maintainer guidance instead of expanding the contributor code of conduct beyond community behavior

🔄 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/4130 **Author:** [@zjy-dev](https://github.com/zjy-dev) **Created:** 5/1/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `clarify-maintainer-responsiveness` --- ### 📝 Commits (1) - [`7d14273`](https://github.com/sindresorhus/awesome/commit/7d14273703f08a54731a6a3472eaedddc744d5bc) Clarify maintainer responsiveness expectations ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `create-list.md` (+1 -0) </details> ### 📄 Description ## Summary - add a short note to the list creation guide that maintainers should review issues and pull requests within a reasonable time - suggest asking additional maintainers for help when updates start to pile up ## Why - addresses #748 by setting expectations for prospective list maintainers before they submit a list - keeps the change focused on maintainer guidance instead of expanding the contributor code of conduct beyond community behavior --- <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-05-08 00:18:34 -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#21152
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?