Removing the project attribute that unbinding seems to remove does not, by itself, have an effect, and I can't see any other diffs between the two clones (one "real", one non-git-enabled now). I tried unbinding in a separate clone and then copying the resultant project file, but that didn't seem to have an effect. So the Flare version of Git is not useful to us, and every time we open the project at the beginning of the day it asks us if we want to pull the latest version, which is annoying and time-consuming because it has to time out.īUT.if we unbind the project from source control, our existing git doesn't work because it removes. fltar files, and the variable files just create placeholders.)
(Possibly an incorrect setup but legacy now: the appropriate values for variables are in the. This is the big loser for us, because we put much of /Project under source control so we can restore old target files when we reproduce an older document.
#MADCAP SUPPORT FREE#
It will point to your git repository if you import the project, but (in the copious free time I have to research such things) it puts only the Contents of the /Content directory under source control. Unless you're specifically using Glaregit, don't: it points to the MadCap git repository, which is probably not what you want. With the new version, it asks to pull the current version of the source (as others have noted).
andy_smith Propeller Head Posts: 14 Joined: Wed 5:41 amįrankly, I don't know any more if I've upgraded, because this whole thing has ustrating.Ĭontext: We use Git, but we have always used it outside of Flare, with Sourcetree or with the command line tools, depending on the comfort level of the individual writer. This is a little alarming as I should only be working with files on my C drive. I've googled that and discovered that this indicates I'm working on a file that has been checked out. I've since noticed that I'm getting a red tick in the file name tab at the top of the main edit window (not in all files though, it doesn't appear in Targets). Are people still rolling this back? How is the rollback performed, through the Windows control panel or is there a feature within Flare?
#MADCAP SUPPORT UPGRADE#
I got the upgrade notification today, 19th January. I notice that this thread started in December. Is this a new default? Can I switch Git off? These popups seem to have gone away now although I may not have triggered them.Īs a team we use Git outside of Flare but Flare 2021 r3 seem to be imposing its Git functionality on me. I seem to have been able to cancel out of these popups and get to my Target file. When I open a target (I’ve not see the popup on any other files yet) it’s asking for public and private keys on a popup titled Certificate Specification. To which I said no as I had done that this morning.
#MADCAP SUPPORT UPDATE#
We treat the files in our Git folder as standalone local files and perform git push/pull updates at the beginning and end of every day.Īfter running the Flare 2021 r3 update today I started getting messages asking me if I want to pull the latest repository whenever I start Flare. We use Git here but we have never used the Git tools in Flare. Like some sort of fool I instantly installed the Flare 2021 r3 update today.
0 kommentar(er)
