detect "dirty" git working tree

[NZJKOL]

Describe the issue

When deploy/update a bundle, it will show the Git Branch and Commit Hash-ID.
But if the user has un-committed changes, this technically not correct.

Configuration

Just change any of the files being synced, in your local Git checkout, and do a deploy without doing a "git add / commit" first.

Expected Behavior

It should some how show that the deploy is "dirty", possibly by just suffixing the Commit Hash-ID with -dirty
An example how it can be detected (there might be better options):

[[ -n `git status -s` ]] && echo "dirty"

If it could also detect if the commit is local-only or also pushed to "remote origin", would be a really cool bonus!

Actual Behavior

It just shows the last committed Hash ID, which doesn't reflect that the files and resources might be different than the source-of-truth.

[pietern]

Thanks for posting the issue.

You're right, this is not implemented. The reasoning for not including it out of the gate is that seeing this metadata is primarily helpful for jobs deployed from automation, where the tree will typically be clean and the commits remote.

We'll consider this. I agree that this isn't complete as-is.