Following are definitions for some of the common phrases used in Flare's integrated source control with Git.
- Bind This means to connect your project to Git. After doing this, you can then take advantage of all the automated source control tasks (such as commit, revert, pull, push, and so on).
- Commit This means to record changes to your Flare files to the local Git repository.
- Revert This means to undo changes you have made to a Flare branch or file. Changes are reverted to the way they were at the last commit.
- Synchronize This pulls the files from the remote Git repository and merges them with your local database, then pushes your local changes back to the remote Git repository.
- Pull This retrieves commits from the remote Git repository and merges them with the files in your local database.
- Push This sends commits from your local database to the remote Git repository.
- Branch This creates a new path for commits. This lets you create new versions of a file while keeping the original file unchanged (e.g., for documenting a new feature, testing page layouts, or rewriting existing information). You can create as many branches as you want.
Note Flare integrates with multiple source control providers to provide built-in source control support. Each of the source control providers built-in to Flare uses different terms. As such, Flare's source control interface is different depending on which source control provider you use. Please refer to the sections for each source control provider if you need to see information about the terms used by other built-in systems.
