Compare commits

...

3 commits

Author SHA1 Message Date
June 4afbebcf4a
ci: add a black job to the style.yaml workflow running black --check
All checks were successful
/ black (push) Successful in 25s
/ ruff (push) Successful in 25s
2024-06-08 23:43:51 +02:00
June 22c23ba3d6
ci: add a style.yaml workflow with a ruff job running ruff check
All checks were successful
/ ruff (push) Successful in 25s
2024-06-08 23:41:32 +02:00
June db3e05e6da
docs: introduce new "ci" tag for changes to the CI and its configuration 2024-06-08 23:14:54 +02:00
2 changed files with 24 additions and 0 deletions

View file

@ -0,0 +1,23 @@
# Links & Resources:
# - https://hatch.pypa.io/latest/install/#github-actions
# - https://docs.astral.sh/ruff/integrations/#github-actions
# - https://black.readthedocs.io/en/stable/integrations/github_actions.html
on: push
jobs:
ruff:
runs-on: docker
steps:
- uses: actions/checkout@v4
- name: Install Hatch
uses: https://github.com/pypa/hatch@install
- name: Run Ruff
run: hatch run lint:ruff check --output-format=github .
black:
runs-on: docker
steps:
- uses: actions/checkout@v4
- name: Install Hatch
uses: https://github.com/pypa/hatch@install
- name: Run Black
run: hatch run lint:black --check --diff .

View file

@ -21,6 +21,7 @@ The `tag` should be one of the following:
- `test` - for adding or correcting tests
- `style` - for changes to the linter or formatter configuration and its results
- `docs` - for changes to documentation only
- `ci` - for changes to the CI and its configuration
- `other` - for anything that isn't covered by the tags above
If a change is a breaking change then that should be indicated by adding a `!` after the tag.