Which Files Can Be Included for Source Control?
You can include files for source control automatically using Flare's built-in integration or you can add them manually in a source control client.
[Menu Proxy — Headings — Online — Depth3 ]
If Using the Source Control Integration in the Flare Interface
If you are using Flare's built-in source control integration, you can include the following types of files:
- The main FLPRJ file
- All files from the Content folder
- All files from the Project folder, except those in the Project > Users subfolder
- Files from a specific Output subfolder, if using source control publishing
In most workflows, you only need to transfer the content and project files mentioned, and when you are ready to generate output, you would publish the output files to another location where users can access them (such as a website or network drive). However, if you want to use Flare to directly publish your output to source control (e.g., so you can keep a copy of your finished output for future reference), you can also create a source control publishing destination.
If Adding Files Manually in Your Source Control Client
If you are manually adding files to a source control application (rather than using the built-in Flare integration), you can transfer any appropriate files in a Flare project. These include the following:
- The main FLPRJ file
- All files from the Content folder
- All files from the Project folder, except those in the Project > Users subfolder
-
Files from a specific Output subfolder
You might transfer output files to source control, for example, if you are integrating your Help into a desktop application, and programmers need access to your output files to build the application. However, if you do this, make sure you map the source control to the appropriate output subfolder, and not to the Temporary subfolder or to the main Output folder, which contains the Temporary subfolder.
