The llama-cpp-agent framework is a tool designed for easy interaction with Large Language Models (LLMs). Allowing users to chat with LLM models, execute structured function calls and get structured output. Works also with models not fine-tuned to JSON output and function calls.
Other
445
stars
38
forks
source link
Enhance CI workflow to include package publishing to PyPI #48
This pull request enhances the existing CI workflow to streamline the process and include the publishing of the package to PyPI within the same workflow. The changes made in this PR offer the following improvements:
Consolidated Workflow: The separate publish workflow YAML file has been removed, and the publishing step has been integrated into the main CI workflow. This consolidation simplifies the overall configuration and reduces duplication.
Conditional Publishing: The publishing step is now triggered conditionally based on the release event. By utilizing the on and if keywords, the publishing step is executed only when a release is published. This ensures that the package is published to PyPI only when a new release is created, providing better control over the publishing process.
Artifact Handling: The CI workflow now includes steps to upload and download the built package as an artifact. This allows the publishing job to access the package files without rebuilding them, saving time and resources.
Improved Efficiency: The changes made in this PR streamline the CI and publishing process, reducing the overall execution time and minimizing the maintenance overhead of managing separate workflow files.
The updated CI workflow YAML file now includes the following key components:
The on section triggers the workflow on both push events to the main branch and release events with the type published.
The build job remains unchanged and is responsible for building the package.
An additional step is added to the build job to upload the built package as an artifact.
A new publish job is introduced, which depends on the successful completion of the build job.
The publish job includes a condition to ensure it only runs when a release is published.
The publish job downloads the artifact and uses the pypa/gh-action-pypi-publish action to publish the package to PyPI.
By merging this pull request, the CI workflow will be enhanced to handle both the continuous integration and the publishing of the package to PyPI in a more efficient and streamlined manner.
Please review the changes and provide any feedback or suggestions for further improvements.
This pull request enhances the existing CI workflow to streamline the process and include the publishing of the package to PyPI within the same workflow. The changes made in this PR offer the following improvements:
Consolidated Workflow: The separate publish workflow YAML file has been removed, and the publishing step has been integrated into the main CI workflow. This consolidation simplifies the overall configuration and reduces duplication.
Conditional Publishing: The publishing step is now triggered conditionally based on the release event. By utilizing the
onandifkeywords, the publishing step is executed only when a release is published. This ensures that the package is published to PyPI only when a new release is created, providing better control over the publishing process.Artifact Handling: The CI workflow now includes steps to upload and download the built package as an artifact. This allows the publishing job to access the package files without rebuilding them, saving time and resources.
Improved Efficiency: The changes made in this PR streamline the CI and publishing process, reducing the overall execution time and minimizing the maintenance overhead of managing separate workflow files.
The updated CI workflow YAML file now includes the following key components:
onsection triggers the workflow on bothpushevents to themainbranch andreleaseevents with the typepublished.buildjob remains unchanged and is responsible for building the package.buildjob to upload the built package as an artifact.publishjob is introduced, which depends on the successful completion of thebuildjob.publishjob includes a condition to ensure it only runs when a release is published.publishjob downloads the artifact and uses thepypa/gh-action-pypi-publishaction to publish the package to PyPI.By merging this pull request, the CI workflow will be enhanced to handle both the continuous integration and the publishing of the package to PyPI in a more efficient and streamlined manner.
Please review the changes and provide any feedback or suggestions for further improvements.