some thoughts on what I think we'll want for ci on this:
Is the plan to do this on main?
I think we should, yes
Richard Feldman said:
I think we should use a separate folder but not a separate branch
better to just keep merging stuff into
main
since we're not going to cause merge conflicts with any existing PRs anyway :big_smile:
From the other thread
Cool, I'll make a PR with the tokenizer stuff I did then
To make iteration go fast, we should figure out some CI stuff early. We want zig PRs to only trigger zig ci and rust PRs to only trigger rust ci. For now, zig ci probably can just be calling zig build test
or zig test main.zig
or something like that.
On top of that, getting musl and static builds setup early likely will help avoid headaches later.
@Anton do you think we should use the same ci manager or a separate workflow?
ci-manager should probably do a zig folder change check and forward to a new zig-ci-manager workflow.
Last updated: Jul 06 2025 at 12:14 UTC