infocommand 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.
:commitwhen a Polylith workspace is created, these
gitcommands are executed:
create workspacecommand, then we have to perform these (or similar) commands manually.
git logfrom the workspace root, it returns something like this:
stable point in timeof 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: c91fdadand this is because it refers to this SHA-1 hash in git.
developmentprojects, and the
clibricks are all marked with an asterisk,
*. The way the tool calculates changes is to ask
gitby running this command internally:
*signs come from. The paths that start with
bases/cli/makes the tool understand that
infocommand 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 timeto our second commit.
diffcommand 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 diffcommand will also return the workspace directory in the path (which is stripped away by the
polytool). This directory can be shown by running the
poly ws get:ws-local-dircommand.