Open dotkas opened 4 years ago
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.
See the documentation on zest.releaser
entry points.
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?