feat: run the generated project's CI workflow directly - #120
Merged
Merged
Conversation
bardiharborow
marked this pull request as ready for review
June 24, 2026 05:37
bardiharborow
marked this pull request as draft
June 24, 2026 05:37
bardiharborow
force-pushed
the
feature/run-generated-project-ci
branch
4 times, most recently
from
June 24, 2026 11:52
c765b0a to
84bfdc8
Compare
bardiharborow
force-pushed
the
feature/run-generated-project-ci
branch
from
June 24, 2026 12:42
84bfdc8 to
810de9a
Compare
bardiharborow
force-pushed
the
feature/run-generated-project-ci
branch
4 times, most recently
from
June 24, 2026 23:21
203db94 to
6abdd5f
Compare
This commit modifies the template's CI workflow to run the generated project's CI workflow directly rather than running a more limited set of tests.
Copier does not emit the `uv.lock` and `package-lock.json` files, but they are needed for the Docker image. This commit adjusts the CI workflow to generate these and adds similar instructions to the README for developers creating new projects.
act runs a workflow's jobs concurrently by default, sharing a single host toolcache between the job containers. astral-sh/setup-uv installs uv to a shared path, so one job writing the binary while another execs it races and fails with ETXTBSY ("Text file busy", exit 126). This commit passes `--concurrent-jobs 1` so the jobs run serially, matching the isolation real GitHub Actions gives each job on its own runner.
Under act, a non-container job with services runs on the host network and `${{ job.container.network }}` is empty. This commit adds quotation marks around it when it is passed as a CLI argument to avoid crashing.
This commit also modifies the image build job to distinguish between a network not being provided and there being no network, and avoiding fabricating a network in the latter case.
bardiharborow
force-pushed
the
feature/run-generated-project-ci
branch
from
June 24, 2026 23:25
6abdd5f to
17550d2
Compare
bardiharborow
marked this pull request as ready for review
June 24, 2026 23:44
a-musing-moose
approved these changes
Jun 25, 2026
a-musing-moose
left a comment
a-musing-moose
left a comment
Contributor
There was a problem hiding this comment.
Neat, I do found the output of act a little overwhelming compared to actual CI runs but this is a nice way to make sure the embedded CI actions actually work.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR modifies the template's CI workflow to run the generated project's CI workflow directly rather than running a more limited set of tests.