Open simonw opened 4 years ago
This also means the bot that lands the submission can handle assigning it a unique ID and putting it in the correct place in the directory structure.
And the landing bot can bake in the added timestamp.
I put together enough of a proof of concept that I'm convinced this is worth pursuing.
Here's how it's going to work:
$ID.yaml
file with the content plus extra id:
and publish_date:
fields.A separate process can then compile the SQLite database and publish it somewhere with Datasette.
Events I should listen to (from https://help.github.com/en/actions/reference/events-that-trigger-workflows#issue-comment-event-issue_comment)
on:
issue_comment:
types: [created]
issues:
types: [opened, edited]
Does an event fire when I add a reaction to a comment? I'll try that now and see what happens on https://api.github.com/repos/simonw/show-your-workings/events
Asked about issue reaction triggers here: https://github.community/t/trigger-workflow-on-issue-comment-reaction/119961
The comment the bot posts on the issue when it lands the submission could include the instruction to propose further changes by proposing edits to the file, with a link.
An issue template with example YAML in it, combined with a bot that reports back on if the YAML is valid.
Having a repo owner add a shipit reaction or comment could cause the bot to land the submission.
Modifications could be handled by regular pull requests. It would just be new submissions that would use issues.