https://github.com/outpost-os/pipeline-python
Outpost related reusable workflows for python repositories
https://github.com/outpost-os/pipeline-python
ci-cd-pipeline python
Last synced: 5 months ago
JSON representation
Outpost related reusable workflows for python repositories
- Host: GitHub
- URL: https://github.com/outpost-os/pipeline-python
- Owner: outpost-os
- Created: 2024-07-09T13:13:09.000Z (almost 2 years ago)
- Default Branch: main
- Last Pushed: 2024-09-19T13:53:26.000Z (over 1 year ago)
- Last Synced: 2025-04-09T18:54:03.798Z (about 1 year ago)
- Topics: ci-cd-pipeline, python
- Homepage:
- Size: 38.1 KB
- Stars: 0
- Watchers: 2
- Forks: 3
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSES/Apache-2.0.txt
- Codeowners: CODEOWNERS
Awesome Lists containing this project
README
# Outpost-OS reusable workflows for Python packages
[](https://api.reuse.software/info/github.com/outpost-os/pipeline-python)
## Introduction
This repository hold the python-related reusable workflows in order to limit redundancy between each python package CI/CD usage.
This repository also impose some restrictions on python packages quality and tooling for Outpost, such as:
- using ToX for manipulating python venv and proper targets
- having the following tox targets:
- unittests for unit testing
- docs for doc generation
- lint for linting
## Workflows
The following workflows exists:
- doc.yml: built for running tox docs target
- unittest.yml: built for executing tox unittests target
- lint.yml: built for executing tox lint target
## reusable workflows usage
Reusing workflows is made in the way described in [Github docs](https://docs.github.com/en/enterprise-cloud@latest/actions/using-workflows/reusing-workflows)
the lonely required input, shared by all workflows is `python-version`, that
define the python release to execute the workflow on.
A typical usage is the following:
```
uses: outpost-os/pipeline-python/.github/workflows/lint.yml@v1
with:
python-version: '3.12'
```