You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- name: RenderCV
run: |
cd src
cv_file=$(find . -maxdepth 1 -type f -name "*_CV.yaml" | head -n 1)
if [ -z "$cv_file" ]; then
echo "No RenderCV file found!"
exit 1
fi
cd ..
rendercv render src/$cv_file --pdf-path ${cv_file%.yaml}.pdf --markdown-path README.md --latex-path ${cv_file%.yaml}.tex
When I use customer theme, rendercv can't find theme folder after cd .., because current path is not in src/
Perhaps should:
Add a parameter for rendercv render to locate theme folder.
Use a specific fix folder to contain all theme folders.
Copy theme folder to root path of the project after cd ... But we don't know the name of customer theme.
By the way, this workflow can only render one yaml. If I have several yaml files in src/, the others will be ignored. should we use a for loop to render all yaml?
The text was updated successfully, but these errors were encountered:
I like the specific folder for theme folders (just themes?), since that would be extremely easy to read.
I think with just a CLI flag, you'll end up with a lot of issues getting made with people having this same problem, whereas a theme folder would be pretty clear.
For the workflow, I think it'd be great if it could take a (or many) yaml files. Maybe a --all to use all of the different files one could have (and default to this), and otherwise have a -filename resume.yaml flag for if someone only wants a specific one?
In github workflow,
When I use customer theme,
rendercv
can't find theme folder aftercd ..
, because current path is not insrc/
Perhaps should:
rendercv render
to locate theme folder.cd ..
. But we don't know the name of customer theme.By the way, this workflow can only render one yaml. If I have several yaml files in
src/
, the others will be ignored. should we use a for loop to render all yaml?The text was updated successfully, but these errors were encountered: