-
Notifications
You must be signed in to change notification settings - Fork 86
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
auto-generated readmes #71
Milestone
Comments
The right way to do this would be to write a tool that generates these from the script files, and to then have the directory's Holmakefile try to generate one such in every directory. |
@myreen so is this done now? |
I thought the plan is to only close this issue once practically all files
produce readme entries. Currently hardly any do, but the infrastructure is
there.
…On Tue, 28 Feb 2017 at 13:29, Ramana Kumar ***@***.***> wrote:
@myreen <https://github.com/myreen> so is this done now?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#71 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AA8731HVTPbrXVoQbOUtHFaWO60Czefzks5rhAsQgaJpZM4F4h2g>
.
|
Perhaps we could make a list of files/directories that still need READMEs and assign people here? |
xrchz
added a commit
that referenced
this issue
Aug 11, 2018
xrchz
added a commit
that referenced
this issue
Aug 13, 2018
xrchz
added a commit
that referenced
this issue
Aug 14, 2018
xrchz
added a commit
that referenced
this issue
Aug 14, 2018
xrchz
added a commit
that referenced
this issue
Aug 15, 2018
xrchz
added a commit
that referenced
this issue
Aug 15, 2018
xrchz
added a commit
that referenced
this issue
Aug 15, 2018
myreen
added a commit
that referenced
this issue
Nov 28, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
generating the readme content from comments in the files in the directory could be one way to avoid it going too stale.
The text was updated successfully, but these errors were encountered: