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
I have a large compile file generated in my Python package which is ignored in .gitignore, but needs to be included in the .tar.gz that release creates.
The file is generated on-the-fly between prerelease and release in my build CI.
Since it seems Zest checks out all code in a clean, temporary repository, this file is not included in the release.
How do I include this file in the release bundle being sent up?
The text was updated successfully, but these errors were encountered:
You would need to create a zest.releaser extension to handle this. A good example would be zest.pocompile. This uses a zest.releaser hook that runs after a fresh copy has been made, and compiles .po files to .mo files.
Hi.
I have a large compile file generated in my Python package which is ignored in
.gitignore
, but needs to be included in the.tar.gz
thatrelease
creates.The file is generated on-the-fly between
prerelease
andrelease
in my build CI.Since it seems Zest checks out all code in a clean, temporary repository, this file is not included in the release.
How do I include this file in the release bundle being sent up?
The text was updated successfully, but these errors were encountered: