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
In my builds, I have a separate step for GH release creation that uses a trimmed version of my manual changelog (similar issue to #71). A while back, I used to be able to run this with options -o -e -c -l to avoid re-fetching externals, re-localizing, re-copying files, and so on. Unfortunately, a change was made to cause option -c (skip_copying) to also turn off uploading entirely: cf2276c#diff-8bc94a3006768345d17c827c0bb5840e6e4daee6de1c2b1ea672f53f162d171dR117
Looking at that commit message, it feels like this change was maybe unintentional? In any case, it would be nice to be able upload a different changelog to the GH release without having to re-build the entire addon.
The text was updated successfully, but these errors were encountered:
In my builds, I have a separate step for GH release creation that uses a trimmed version of my manual changelog (similar issue to #71). A while back, I used to be able to run this with options
-o -e -c -l
to avoid re-fetching externals, re-localizing, re-copying files, and so on. Unfortunately, a change was made to cause option-c
(skip_copying) to also turn off uploading entirely: cf2276c#diff-8bc94a3006768345d17c827c0bb5840e6e4daee6de1c2b1ea672f53f162d171dR117Looking at that commit message, it feels like this change was maybe unintentional? In any case, it would be nice to be able upload a different changelog to the GH release without having to re-build the entire addon.
The text was updated successfully, but these errors were encountered: