feat(ci): refactor workflows using reusable workflow pattern #46
+144
−119
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
OttoAllmendinger
force-pushed
the
BTC-0.consolidate-workflows
branch
5 times, most recently
from
ea4ffac to
9077838
Compare
Create a reusable build-and-test workflow that can be used by both CI and publish workflows. This reduces duplication and ensures consistent build/test procedures across different workflows. Notably this now uses caching in the publish workflow as well. Issue: BTC-0 Co-authored-by: llm-git <llm-git@ttll.de>
OttoAllmendinger
force-pushed
the
BTC-0.consolidate-workflows
branch
from
9077838 to
454f855
Compare
lcovar
approved these changes
Nov 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Create a reusable build-and-test workflow that can be used by both CI
and publish workflows. This reduces duplication and ensures consistent
build/test procedures across different workflows.
Notably this now uses caching in the publish workflow as well.
Issue: BTC-0