Post History

I received a response from Flare's technical support.  There was a bug in Flare's git integration in some older versions (at least 2019r2; not sure how much farther back).  This bug was fixed in Flare 2020, but the result is that if people are using mixed versions, as we are, then there's a tug of war between the Flare clients.  So long as we were *all* on Flare 2019 the bug didn't manifest, but once some group members moved to 2020, we had a problem.  Madcap strongly recommends that we all move to the latest version.  

It's also possible that somebody still has [git binding](https://help.madcapsoftware.com/flare2020r3/Content/Flare/Source-Control/Git/Process/Binding-Project-Source-Control-Git.htm#AutomaticallyDetectingProjectBindings) turned on -- or perhaps somebody upgraded and failed to turn it off again.  (Flare upgrades don't transfer your settings, unfortunately; you have to start over.  Which is why some of us never upgraded to 2020 -- too much hassle.)

In the meantime, write-protecting .gitignore locally, as suggested in a comment here, works.