lars/giant
1
0
Fork 0
Code Issues 2 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

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
Conversation 0 Commits 2 Files Changed 3
+36 -7
lars commented 2026-08-28 13:06:59 +02:00
Owner
Copy Link
Copy Source
  • 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.
- 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.
lars added 1 commit 2026-08-28 13:07:01 +02:00
ci: give automated commits visible checks, scope CI triggers, publish releases 7de3e92871 
- 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.
lars added 1 commit 2026-08-28 13:08:30 +02:00
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
cc11efb3ae 
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.
lars merged commit b0998a7d86 into master 2026-08-28 13:14:20 +02:00
lars deleted branch ci/pr-scoped-checks-and-package-publish 2026-08-28 13:14:20 +02:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
architecture
bug
Silent/wrong behavior, no crash
 experiment
feature
New feature matching the v0.3 redesign
 investigation
modularity
Making the network genuinely pluggable
 performance
phase2
validation
wontfix
Not being fixed right now
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
lars (Lars Bogner)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: lars/giant#90
Delete Branch "ci/pr-scoped-checks-and-package-publish"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?