moon ci | --stdin use cases

[nhomble]

Partially related discussion from the past: #1645

---

We'd like to use moon ci to be efficient with our pipeline resources, but we're unsure of how to use moon ci given we are generating some source code along the way. The confusion is that we're unclear how moon ci detects touched_files. Since we do not commit our generated code into main, HEAD would not contain our generated code. So far, we've been explicitly running our :codegen task and then rerunning a general :build across the project.

Two questions:

1. can moon ci consider uncommitted changes in the local workspace beyond what is committed on HEAD?
2. is this what the --stdin flag was intended for?

[milesj]

Yeah right now, touched files in CI are gathered with git diff, which should capture unstaged files. It's represented by the U flag. Would need to verify though: https://github.com/moonrepo/moon/blob/master/crates/vcs/src/gitx/tree.rs#L330

However, the --stdin flow does allow you to pass a custom list of touched files. It basically allows for this moon query touched-files | moon ci --stdin, or echo "some/path\nanother/path" | moon ci --stdin.

[milesj]

Let me see if git diff needs extra args or something for unstaged.

[nhomble]

If you'd like, I can come up with an example project + pipeline.

Additionally, I can migrate this to an issue if it helps organize.

[nhomble]

https://git-scm.com/docs/git-status#_short_format

do you think git status -s is closer to what you're looking for?

[milesj]

We actually run git status but only locally. Can probably change it for CI also.

[milesj]

Updated 1.41.5 to include uncommitted files. Let me know if that works.