mirror of
https://github.com/awesome-selfhosted/awesome-selfhosted.git
synced 2026-03-09 03:33:15 -05:00
Require more information if ⚠ is added to a project? #4147
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/awesome-selfhosted#4147
Reference in New Issue
Block a user
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?
Originally created by @e-alfred on GitHub (Apr 5, 2017).
Hello,
would it be possible to require more information to be added if ⚠ is added to some project? This would make it easier for viewers to find out what external service/component is needed that the user can't control.
@ghost commented on GitHub (Apr 5, 2017):
I think that is a great idea. It could come after the name of the project so that if someone sees this: ⚠ they can go find out more information themselves and also be contributing to the project.
@nodiscc commented on GitHub (Apr 5, 2017):
Reasons for marking a project with the ⚠ symbol are listed in corresponding issues/pull requests. Usually you can just search for the project in the issues tracker to go back to discussion surrounding that project.
Eg. https://github.com/Kickball/awesome-selfhosted/issues?q=poffer returns https://github.com/Kickball/awesome-selfhosted/pull/739 which has more information about the Poffer ⚠ entry.
I don't think the markdown file itself is appropriate to detail that kind of info (we try to keep it readable by not stuffing it with details, it's already quite large).
Is there software which is marked ⚠ for an unclear reason? If that info is missing, we can add it to the relevant archived pull request/issue.
@nodiscc commented on GitHub (Apr 12, 2017):
Closing, feel free to reopen if needed. Referencing in #89
@melvinmezzy commented on GitHub (Feb 15, 2022):