|
| 1 | +# "Check Poetry" workflow (Task) |
| 2 | + |
| 3 | +Check for problems with configuration files of the [**Poetry**](https://python-poetry.org/) Python package manager. |
| 4 | + |
| 5 | +This is the version of the workflow for projects using the [Task](https://taskfile.dev/#/) task runner tool. |
| 6 | + |
| 7 | +## Installation |
| 8 | + |
| 9 | +### Workflow |
| 10 | + |
| 11 | +Install the [check-poetry-task.yml](check-poetry-task.yml) GitHub Actions workflow to `.github/workflows/` |
| 12 | + |
| 13 | +### Assets |
| 14 | + |
| 15 | +- [`Taskfile.yml`](assets/check-poetry-task/Taskfile.yml) - Validation tasks. |
| 16 | + - Install to: repository root (or merge into the existing `Taskfile.yml`). |
| 17 | +- [`Taskfile.yml`](assets/poetry-task/Taskfile.yml) - Installation task. |
| 18 | + - Merge into `Taskfile.yml` |
| 19 | + |
| 20 | +## Readme badge |
| 21 | + |
| 22 | +Markdown badge: |
| 23 | + |
| 24 | +```markdown |
| 25 | +[](https://github.com/REPO_OWNER/REPO_NAME/actions/workflows/check-poetry-task.yml) |
| 26 | +``` |
| 27 | + |
| 28 | +Replace the `REPO_OWNER` and `REPO_NAME` placeholders in the URLs with the final repository owner and name ([example](https://raw.githubusercontent.com/arduino-libraries/ArduinoIoTCloud/master/README.md)). |
| 29 | + |
| 30 | +--- |
| 31 | + |
| 32 | +Asciidoc badge: |
| 33 | + |
| 34 | +```adoc |
| 35 | +image:https://github.com/{repository-owner}/{repository-name}/actions/workflows/check-poetry-task.yml/badge.svg["Check YAML status", link="https://github.com/{repository-owner}/{repository-name}/actions/workflows/check-poetry-task.yml"] |
| 36 | +``` |
| 37 | + |
| 38 | +Define the `{repository-owner}` and `{repository-name}` attributes and use them throughout the readme ([example](https://raw.githubusercontent.com/arduino-libraries/WiFiNINA/master/README.adoc)). |
| 39 | + |
| 40 | +## Commit message |
| 41 | + |
| 42 | +``` |
| 43 | +Add infrastructure for checking Poetry configuration files |
| 44 | + |
| 45 | +The project's Python package dependencies are managed using the "Poetry" tool. |
| 46 | + |
| 47 | +Tasks and a GitHub Actions workflow are added to maintain and check for problems in the Poetry configuration files. |
| 48 | + |
| 49 | +The tasks provide the following operations: |
| 50 | + |
| 51 | +* Check for problems with the data structure of the `pyproject.toml` Python project file |
| 52 | +* Update the `poetry.lock` file as may be required following manual modifications to `pyproject.toml`, or update of the |
| 53 | + "Poetry" application |
| 54 | + |
| 55 | +These tasks are executed by the GitHub Actions workflow on any push or pull request that modifies relevant files, and |
| 56 | +periodically to check for breakage caused by external changes. |
| 57 | +``` |
| 58 | +
|
| 59 | +## PR message |
| 60 | +
|
| 61 | +```markdown |
| 62 | +The project's Python package dependencies are managed using the [**Poetry**](https://python-poetry.org/) tool. |
| 63 | +
|
| 64 | +[Tasks](https://taskfile.dev/) and a GitHub Actions workflow are added to maintain and check for problems in the **Poetry** configuration files. |
| 65 | +
|
| 66 | +The tasks provide the following operations: |
| 67 | +
|
| 68 | +- Check for problems with the data structure of the [`pyproject.toml`](https://python-poetry.org/docs/pyproject/) Python project file |
| 69 | +- Update the `poetry.lock` file as may be required following manual modifications to `pyproject.toml`, or update of the **Poetry** application |
| 70 | +
|
| 71 | +These tasks are executed by the GitHub Actions workflow on any push or pull request that modifies relevant files, and periodically to check for breakage caused by external changes. |
| 72 | +``` |
0 commit comments