In my project, I rely on git describe ... --dirty to produce version info into the source code that gets compiled for a target machine.
This works well enough, except that in many cases, the main project file needs a tiny adjust before compilation to work (changing the machine IP address). This will flag the clone as 'dirty' and append the -dirty suffix to the version info visible in the application.

This behavior is technically correct, but in my case unwanted, as it makes it look like all machines have cowboy-coded changes, though they don't necessarily.

Can I make an exception for a particular file for the -dirty state in GIT?

I do need this file tracked in the repository.