Add a workflow for generating contributor pages #18

Merged
mih merged 1 commit from msz/www.trr379.de:contributor-pages-workflow into main 2026-02-12 04:58:14 +00:00
Contributor

This is a draft of how a workflow for creating publication pages could look like. The key step is in "Process metadata".

I am not 100% sure whether everything is done 100% correctly (can I write intermediate files to /tmp? can I install dtc and qrg separately?) but the best way of testing that I can see is in action 1.

An outcome of running an analogous command locally (after deleting existing markdown pages) is in #17 - because that PR also contains some manual tweaks (moving portraits where pid / folder name changed), I suggest merging that preview PR first.


  1. This statement should not, by any means, be taken as a refusal to do anything else. That this is the best way I can see does not mean that there is no better way, and I am happy to take suggestions ↩︎

This is a draft of how a workflow for creating publication pages could look like. The key step is in "Process metadata". I am not 100% sure whether everything is done 100% correctly (can I write intermediate files to `/tmp`? can I install dtc and qrg separately?) but the best way of testing that I can see is in action [^1]. An outcome of running an analogous command locally (after deleting existing markdown pages) is in #17 - because that PR also contains some manual tweaks (moving portraits where pid / folder name changed), I suggest merging that preview PR first. [^1]: This statement should not, by any means, be taken as a refusal to do anything else. That this is the best way *I can see* does not mean that there is no better way, and I am happy to take suggestions
@ -0,0 +69,4 @@
- name: Commit and push updates
id: commit
run: |
git add content/publications
First-time contributor

I have not run the code in this action, but I noticed when skimming though that the "process metadata" step uses person.py to create contents in {...}/contents/contributors, but this git add stages content/publications, and the commit message is on updating publication. Am I missing something, or is this a copy-paste error from a different action?

I have not run the code in this action, but I noticed when skimming though that the "process metadata" step uses ``person.py`` to create contents in ``{...}/contents/contributors``, but this ``git add`` stages ``content/publications``, and the commit message is on updating publication. Am I missing something, or is this a copy-paste error from a different action?
Author
Contributor

Copy-paste error. I knew it wouldn't work on the first try - thank you for spotting that!

Copy-paste error. I knew it wouldn't work on the first try - thank you for spotting that!
msz marked this conversation as resolved
msz force-pushed contributor-pages-workflow from 7cdcc1d49d to 22de46eedc 2026-02-11 16:28:00 +00:00 Compare
msz changed title from WIP: Add a workflow for generating contributor pages to Add a workflow for generating contributor pages 2026-02-11 16:31:51 +00:00
mih merged commit 9a0efe702d into main 2026-02-12 04:58:14 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
q04/www.trr379.de!18
No description provided.