Interesting. I will take a look tomorrow. Thanks.

Can we still make CI work well if the Chez Scheme sources are merged as a subtree into the racket repo? (Using a subtree solves various other problems, and submodules do not appear to be a good option to solve those other problems.)

@mflatt Yes - it can still work well. We can ensure that Chez workflows are only triggered when files inside the subtree change. I think this is actually a good idea.

I will change the CI as soon as you do the merge.

This actually solve a big CI problem on the racket side which is that racket currently clones Chez to build racket cs, which means that racket can fail a build even if nothing in racket changes.