Knife Spork metadata and CI

For chef cookbooks in jenkins ci, I just tried to replace Thor ScmVersion
for bumping the cookbook numbers with knife spork. After successful tests,
the job would run knife spork which would bump the version number in
metadata.rb. That change needed to be committed back to git, or the release
number would never increase on the next job run.

Well, since the job polls git, the update to metadata.rb also causes a
further build. The result is it’s constantly building the job over and over.

So, if everyone is using knife spork, how do you work around this?