Skip to content
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

Recursive & downloadable outputs example #11

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Recursive & downloadable outputs example #11

wants to merge 2 commits into from

Conversation

stephlocke
Copy link

This goes through each folder and outputs any md files to docx. Github Actions then makes the output directory a zipped download. Developed during problem solving, posted it on https://stackoverflow.com/a/65091856/2257093

This shows how to go off the "happy path" of a simple pandoc call inside github actions and covers common requirements (accessing files and batch transformations).

This goes through each folder and outputs any md files to docx. Github Actions then makes the output directory a zipped download. Developed during problem solving, posted it on https://stackoverflow.com/a/65091856/2257093
@alerque
Copy link
Collaborator

alerque commented Feb 20, 2021

I definitely like this way of working with Actions and employ the model myself quite a bit. That being said, I think this needs a little bit of fleshing out before we can merge it. In particular the README should be documented similarly to the way the other actions are explained. Also somehow we would need to adapt this repository so it would run sensibly on it. I don't want to clutter things up too much, but only having one Markdown file and no directories to work with does make it kind of hard to show off this particular usage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants