Post History
We use Madcap Flare for our documentation, and the project is checked into git. (In case this matters, this is a locally-hosted git server, not GitHub.) The project uses a .gitignore file to aver...
#2: Post edited
by
Monica Cellio
·
2021-02-02T20:10:20Z (almost 4 years ago)
source-control is now the parent tag of git so don't need both (this question is specifically about git)
#1: Initial revision
by
Monica Cellio
·
2021-02-02T20:03:31Z (almost 4 years ago)
How do we get Flare to stop modifying .gitignore?
We use Madcap Flare for our documentation, and the project is checked into git. (In case this matters, this is a locally-hosted git server, *not* GitHub.) The project uses a .gitignore file to avert commits of output files and assorted Flare byproducts that don't belong in source control. We do not use Flare's source-control interface and the project is unbound from git. People use git clients (mostly TortoiseGit) to interact with git, not Flare. Yet, Flare *sometimes* modifies .gitignore. Sometimes people catch this before committing, which is a little frustrating, but sometimes they don't and it gets to a pull request before a reviewer catches it and the person has to remove it. We know we can use a git hook to block those commits, but we'd like to fix the root problem if we can. In our group we have both Flare 2019 and Flare 2020 in use, and currently only the people using Flare 2020 are having this problem, but we've had the problem in the past too, and an [unanswered support thread from 2018](https://forums.madcapsoftware.com/viewtopic.php?f=68&t=30880) suggests the problem is older too. (I also found related discussion from 2016.) Our group isn't large enough to really establish a pattern here; Flare version might be a red herring. Is there something we can do in Flare to get it to stop modifying .gitignore? It shouldn't be touching files that aren't part of the project, but it is. Sometimes. Unpredictably.