Leave file if it exists, but overwrite if there is a new one #1664
Unanswered
stephenpapierski
asked this question in
Q&A
Replies: 2 comments
-
|
I'm also noting that if there are new files that fall under the clean-exclude filters, the script says "There is nothing to commit. Exiting early… 📭". I always want the new files, but want to leave the old files if they exist. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
My current solution to get around this is simply setting clean to false. I don't anticipate having too many files to delete after the fact. I'll still take any recommendations for something cleaner though. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I currently have a workflow to build a fw, then use this script to publish to gh-pages. The artifacts are only generated during the workflow, so I need to keep them around between deployments. My current setup works fine for a single fw, but I run into issues with 2 firmwares. If I use the defaults (clean=true), I lose fw1 when I build fw2.
I tried clean-exclude for all the fw files, but then it seems I don't get any new fw files.
Is there a way to specify files to leave if they already exists, but also overwrite if they have new versions generated?
I'd prefer not to have to exclude fw2+fwx files in the fw1 workflow and exclude fw1+fwx files in the fw2 workflow, etc.
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions