info command again to see the current state of the workspace:stable since: c91fdad (you most likely have another git SHA/hash). To explain what this is, let's take it from the beginning.:commit when a Polylith workspace is created, these git commands are executed::commit to the create workspace command, then we have to perform these (or similar) commands manually. git log from the workspace root, it returns something like this:stable point in time of this workspace which the tool uses when it calculates what changes have been made (up till now). Notice that the first letters of the hash correspond to stable since: c91fdad and this is because it refers to this SHA-1 hash in git.command-line and development projects, and the user and cli bricks are all marked with an asterisk, *. The way the tool calculates changes is to ask git by running this command internally:* signs come from. The paths that start with projects/command-line/, development/, components/user/ and bases/cli/ makes the tool understand that command-line, development, user and cli are changed.info command again, it will return the same result as before, and the reason is that we haven't told git to move the stable point in time to our second commit.diff command returns the same result as git diff SHA --name-only. This i normally true, except for the case when the workspace lives inside a git repo. In that case, the git diff command will also return the workspace directory in the path (which is stripped away by the poly tool). This directory can be shown by running the poly ws get:ws-local-dircommand.