Replies: 2 comments 2 replies
-
Just tested the latter suggestion (CLEAN + TARGET_FOLDER) and it looks like it works as I'd like it to! Should this behaviour be documented in the README perhaps? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Yeah, updating the docs sounds good to me. The docs for |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey!
I have a setup where I maintain multiple versions of my documentation on github pages (one for each tag, these appear as directories named after their respective tags in my gh-pages root directory). These are set to update whenever a new tag is released using the
CLEAN: true
setting for this action. This part works as intended.However I also plan to maintain a
dev
version (in adev
directory) which updates onpush
actions to mydev
branch. I can't setCLEAN: true
here since it would wipe out my tagged documentation. Ideally, I'd like to update thedev
directory but only after cleaning it out, to ensure that we don't have old pages lying around within the directory. Is there a solution for these sorts of setups? Two ways that I can think of to deal with these scenarios are:CLEAN_EXCLUDE
takes a regex, this would be more flexible that listing each of the directories to maintainCLEAN
only affectsTARGET_FOLDER
when both are used in combinationAre these already implemented features (i can't find info on a regex, or special behaviours w/TARGET_FOLDER)? I can imagine this being useful when you want to update only a subset of the gh-pages branch, let me know what you think!
Beta Was this translation helpful? Give feedback.
All reactions