Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | aux/: Update | EuAndreh | 2021-09-01 | 1 | -6/+8 |
| | |||||
* | aux/: Update | EuAndreh | 2021-07-23 | 1 | -14/+19 |
| | |||||
* | aux/: Update, adapt Makefile accordingly | EuAndreh | 2021-06-26 | 1 | -8/+40 |
| | |||||
* | Makefile, README.md: Adapt to changes in aux/ | EuAndreh | 2021-06-26 | 1 | -5/+8 |
| | |||||
* | Update files under aux/ | EuAndreh | 2021-06-07 | 1 | -1/+1 |
| | |||||
* | README.md: Add explicit "Links" and "Releases" sections | EuAndreh | 2021-06-06 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | | | | | 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. | ||||
* | aux/: Use tabs over spaces for .sh files | EuAndreh | 2021-06-06 | 1 | -2/+2 |
| | |||||
* | aux/: Add favicon to generated HTML files | EuAndreh | 2021-06-06 | 1 | -0/+2 |
| | |||||
* | aux/workflow/public.sh: Mark as executable | EuAndreh | 2021-03-23 | 1 | -0/+0 |
| | |||||
* | Add aux/workflow/public.sh, update aux/workflow/README.sh | EuAndreh | 2021-02-23 | 1 | -0/+15 |