Issue:
I have a job where I am doing a simple checkout in a pipeline where I then make a modification to the git repo and push the update. This ends up causing a new build to be launched from either a webhook or polling event but it is a known good push done within the build process.

Resolution:
If there was a way to push which commitID the repo is associated with by doing something like a SCMrefresh step in a pipeline, it would help a new build not be triggered. I could stage the git commit locally to the workspace, update the commitID the job is "building", and then do the push which would stop a new build from triggering.

This is especially useful for things like releases which a new build being triggered does not really make sense since all that was pushed is a new version number.