📖 🤖 manpages als Standard-Set für holm.tools-CLIs #1
Labels
No labels
Compat/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority/Critical
Priority/High
Priority/Low
Priority/Medium
Reviewed/Confirmed
Reviewed/Duplicate
Reviewed/Invalid
Reviewed/Won't Fix
Status/Abandoned
Status/Blocked
Status/Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
holm.tools.public/repo-template#1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
████░░░░░░███████░░░██░░░░░░░░████████░░███░░░░░░░Idee
Jedes holm.tools-CLI bekommt eine manpage als Standard-Set-Item (wie README/CHANGELOG/cliff.toml).
Auslöser
Beim Anbinden von
pwgenz6c(WSM25/mikrotik-manager) musste das Interface erst aus dem Source gelesen werden (usage()+getopts), weil keinman pwgenz6cexistiert. Eine manpage liefert den Informationserhalt sofort.Vorschlag
man/<tool>.1via scdoc/ronn (Markdown-nah) ODER generiert aus demusage()-Block (single source of truth).--help↔ manpage.repo-templateaufnehmen (Scaffold + Standard-Set-Doku), damit neue Tools es erben.