Status with uncommitted changes

status, like every command, reads the splices from the last commit, and push only sends what is committed. So uncommitted changes in a splice's folder need attention even where the splice itself has nothing to do: such a splice moves up, out of the quiet group, with a note.

Output

setup.bash builds this state:

$ build_scenario scenario_many_splices

$ echo "work in progress" >> libs/cli/file.txt

$ echo "more work" >> libs/parser/file.txt

$ git splice status
On branch main

  ahead 1, behind 1  libs/store
  behind 2           libs/http
  ahead 1            libs/parser  uncommitted changes
  up to date         libs/cli     uncommitted changes

  up to date         libs/theme -> master

Output​

Output