diff options
| author | EuAndreh <eu@euandre.org> | 2021-06-06 10:11:14 -0300 |
|---|---|---|
| committer | EuAndreh <eu@euandre.org> | 2021-06-06 10:11:14 -0300 |
| commit | eef3c3e516c1b89f4a30d068a672dd00dd59f7b5 (patch) | |
| tree | 1cad065719ae9e1149944e3f8a9a94c12189145c /src | |
| parent | aux/: Use tabs over spaces for .sh files (diff) | |
| download | remembering-eef3c3e516c1b89f4a30d068a672dd00dd59f7b5.tar.gz remembering-eef3c3e516c1b89f4a30d068a672dd00dd59f7b5.tar.xz | |
README.md: Add explicit "Links" and "Releases" sections
Instead of generating the "Links" and "Releases" sections on the fly
and adding them to the end of the README.md before processing it with
aux/workflow/README.sh, embed those sections directly and use
aux/workflow/assert-readme.sh to make sure the metadata is there.
Before we had:
1. generate "Links" and "Releases" on the fly inside
aux/workflow/README.sh;
2. add those sections to the end of the README.md;
3. use the custom pandoc build command inside the
aux/workflow/README.sh file.
Now we have:
1. embed "Links" and "Releases" in the README.md directly;
2. use aux/workflow/assert-readme.sh to validate the correct metadata;
3. use the vanilla aux/workflow/commonmark.sh to generate the HTML.
Diffstat (limited to 'src')
0 files changed, 0 insertions, 0 deletions