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
Add additional steps to Github Actions workflow that will build a properly-versioned code artifact using poetry build instead of the "version-less" copy of the source code currently generated. These code artifacts can be used in the following ways:
Include new build artifacts in the Github release alongside the existing source code tarball.
Drops the need for poetry-dynamic-versioning and a full git history in:
kenibrewer
changed the title
FeatureRequest: Add build artifacts for merges to main branch
FeatureRequest: Add build artifacts for CI/CD pipeline
Jan 27, 2024
kenibrewer
added a commit
to kenibrewer/pycytominer
that referenced
this issue
Feb 21, 2024
This adds a versioned code artifact to the ci pipeline that can be used during other actions and in Github releases.
Closescytomining#369
Co-authored-by: Dave Bunten <[email protected]>
Feature type
Add new functionality
Change existing functionality
General description of the proposed functionality
Add additional steps to Github Actions workflow that will build a properly-versioned code artifact using
poetry build
instead of the "version-less" copy of the source code currently generated. These code artifacts can be used in the following ways:poetry-dynamic-versioning
and a full git history in:Feature example
Alternative Solutions
No response
Additional information
We should also add a section to
pyproject.toml
that includes files we want/need in our build artifact such as thetests
directory.See: https://python-poetry.org/docs/pyproject/#include-and-exclude
The text was updated successfully, but these errors were encountered: