Félix Saparelli
Félix Saparelli
Oh, that's interesting and I completely missed that. 🙃 I'm going to have to sit down and figure that one out. As a workaround, you can do something like: ```...
Ugh, I keep forgetting option differences with watchexec. You're right, there is no `-n`, so there's no workaround after all
> I'm not sure how you would support arbitrarily connected commands Ultimately the watchexec runtime will just support running multiple processes natively, so it won't matter. For now, cargo watch...
Right, sorry, an update: as of 5 days ish ago the Watchexec runtime supports this natively (it was not super hard to implement). I've also decided to move Cargo Watch...
What's the status on this, given the above linked PR was merged?
I since scrapped that and have not rewritten it again, so no currently working code to show, sorry!
This would be especially useful to get the raw json before serde parsing so serde failures due to changing APIs can be diagnosed faster
Yes. That would be a conditional around here, if you want to PR this: https://github.com/watchexec/watchexec/blob/main/crates/cli/src/filterer/globset.rs#L23
We can do away with user key management via the same process sigstore works. That is, in CI: 1. Create a key pair 2. Optionally add a certificate to sigstore...
I think that's only for crates, though? not for binary artifacts