If your Flare project is not already bound to a third-party source control tool and you upload the project to Central, you will have only one source control binding. Therefore, you can use the source control connection between your local Flare project repository and the remote Central repository as your primary source control solution. With this model, you can use the Source Control ribbon in Flare to perform regular source control tasks such as committing and synchronizing (i.e., pulling and pushing) files. However, you also have the option of using tools outside of Flare (e.g., Git Bash) to perform source control tasks (e.g., in case there are certain source control tasks not supported in the Flare interface that you need to complete).
How to Use a Single Binding
- Open the project in MadCap Flare.
- Select View > MadCap Central. The MadCap Central window pane opens.
- Be sure to log in if you aren't already.
- Upload (bind) your project to Central.
See Uploading (Binding) Projects.
- In Central, assign users to the new project and make sure they have “Import/Pull” and “Push” permissions. This enables users to import the project using the MadCap Central window pane. It also allows users to push changes up to Central.
See Associating Users With Teams and Projects and Setting User Permissions.
- Newly assigned users must now import the project from Central using the MadCap Central window pane in Flare. This allows each user to work on the project locally.
See Importing Projects.
- In Flare, make changes to your files. Then commit those files and synchronize them (i.e., pull, then push) with the cloned project on Central.
See Committing and Synchronizing in a Single-Bound Model.
Note If your team is using Git branching, you can create branches in Flare and push them up to Central. Other writers on your team who need to work in the same branches can pull them down from Central.