GIT and Imported Shared Project
Posted: Thu May 23, 2019 5:00 am
For me it looks like the Flare developers do not use their own system with GIT integration.
I have already submitted an error report about the constant re-formatting of the .gitignore file, to have the current Flare project paths in the top of the file. This makes GIT believe, that the .gitignore file have changed, when it just moves lines around in the file? Trying to solve this by adding .gitignore to .gitignore
Secondly the problem that a GIT repository can only hold one (as one single) Flare project? We have 34 Flare projects, each making a new copy of the entire GIT repository every time
And now to this question. A known and proposed solution for sharing common files amongst Flare projects is to import a shared Flare project into each Flare project. Here common topics, images etc. are added to each Flare project by an import from another shared Flare project. Internally Flare handles this by adding a small chain/lock on the imported files to indicate that they should not be changed in the current Flare project, but in the shared Flare project instead. The problem is, that when importing, the shared topics files are copied into the file structure of the current Flare project, making GIT think, that a lot of new files are added to the current Flare project . Somehow you already ignore the changes to .gitignore in the Flare UI, it would be a great idea to also ignore imported shared files, since these must be handled from the other shared Flare project?
How are you people working around all these problems?
-cpede
I have already submitted an error report about the constant re-formatting of the .gitignore file, to have the current Flare project paths in the top of the file. This makes GIT believe, that the .gitignore file have changed, when it just moves lines around in the file? Trying to solve this by adding .gitignore to .gitignore
Secondly the problem that a GIT repository can only hold one (as one single) Flare project? We have 34 Flare projects, each making a new copy of the entire GIT repository every time
And now to this question. A known and proposed solution for sharing common files amongst Flare projects is to import a shared Flare project into each Flare project. Here common topics, images etc. are added to each Flare project by an import from another shared Flare project. Internally Flare handles this by adding a small chain/lock on the imported files to indicate that they should not be changed in the current Flare project, but in the shared Flare project instead. The problem is, that when importing, the shared topics files are copied into the file structure of the current Flare project, making GIT think, that a lot of new files are added to the current Flare project . Somehow you already ignore the changes to .gitignore in the Flare UI, it would be a great idea to also ignore imported shared files, since these must be handled from the other shared Flare project?
How are you people working around all these problems?
-cpede