For the commitId field in gitDetails info in the Harness expressions for env, infra and service, the commit id looks like it’s the commit id of the last change to the file. This value means there is a loss of information. The commit ID that was expected was the commit ID of the commit that was selected when selecting the refspec in the pipeline execution. There are two pieces of information that is lost in the current implementation:

- If the env, infra and service are all in the same repo and the same branch was selected, then the information that was lost was that they came from the same configuration, and what that version was

- If the branch is protected, then the information that is lost is that the selected version came from something that was the head of a protected branch at some point (first parent ancestor of current head of branch)

Both of these are required for audit purposes.