lars/giant

ci: give automated commits visible checks, scope CI triggers, publish releases #90

Merged

lars merged 2 commits from ci/pr-scoped-checks-and-package-publish into master

2026-08-28 13:14:20 +02:00

Author	SHA1	Message	Date
lars	cc11efb3ae	ci: fix pull_request trigger not registering CI / Sync project version with tag (pull_request) Has been skipped Details CI / Lint (ruff check) (pull_request) Successful in 39s Details CI / Format (ruff format) (pull_request) Successful in 43s Details CI / Type check (ty) (pull_request) Successful in 1m6s Details CI / Tests (pull_request) Successful in 3m29s Details CI / Bump version, tag, and update changelog on merge to master (pull_request) Has been skipped Details CI / Publish package to Gitea package registry (pull_request) Has been skipped Details A bare "pull_request:" key parses to null in YAML, which the runner apparently doesn't treat as "trigger with defaults" the way an empty mapping does — the open PR for this branch got no CI run at all.	2026-08-28 13:08:25 +02:00
lars	7de3e92871	ci: give automated commits visible checks, scope CI triggers, publish releases - Drop [skip ci] from the bump-version/changelog/tag-sync commits so master's tip always has a check run instead of only the merge commit. - Filter those chore commits out of the changelog via message pattern instead of the now-removed [skip ci] tag. - Only run CI on push to master (plus tags); pull requests to any branch still run the full suite. - Add a publish-package job that builds and publishes to the Gitea PyPI registry on every tag push, after tests and version sync pass.	2026-08-28 13:06:26 +02:00