Source Control Explorer

If Using 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). See Binding a Project to Git.

• Unbind Provider If you no longer need your project connected to source control, you can remove the connection by "unbinding" the provider. See Unbinding a Git Provider From a Project.

• Disable Provider If you do not want to see the source control interface elements in Flare, you can disable the provider. This does not mean you cannot use source control. As long as the provider is still bound to the project, you can perform source control tasks in a third-party tool outside of Flare. See Disabling a Git Provider.

• Import Project from Source Control If you have a project in Git, you can import it to Flare so you can edit it. See Importing a Project From Git.

• View Pending Changes When you make changes to your project in Flare, you can see the files you have changed in the Pending Changes pane. You can also include or exclude changes if you do not want to check in all of your files at once. See Viewing Modified Files—Git.

• Commit When you are finished editing files, you can commit them to source control. Committing a file adds your changes to the local Git database. It is a good idea to periodically commit files so that they are organized in logical chunks with a comment that accurately summarizes the changes. When you are ready to add your local commits to the remote repository, you can push these files to the remote. Committing and pushing changes frequently can help to avoid conflicting changes from other users, although conflicts are bound to occur from time to time. See Committing Source Control Files—Git.

• Create Branches When you are working in Git, you can create branches. See Creating Branches.

• Switch Branches If you have created more than one branch, you can switch to the branch you want to work with. You will see the files associated with the selected branch, and new commits will be sent to the selected branch. By default, the master branch is selected. See Switching Branches.

• Publish Branches If you have created a branch, you can publish it, which means to copy it to the remote repository. This lets you push to and pull from that branch. See Publishing Branches.

  If another writer on the team wants to get a remote branch that someone else has published and add it locally, they can do the following: (1) Create a new branch locally with the same name as the remote branch; (2) pull the branch from the remote repository.

• Delete Branches If you no longer need a branch, you can delete it. This also deletes any commits on that branch. See Deleting Branches.

• Merge Branches There are times where you may have to merge branches into a common branch. See Merging Branches.

• View and Modify Network Settings You can view and modify your current source control network settings without having to close Flare. You can make changes to several settings, including SSL configurations, HTTP proxy options, and cookies. See Modifying Network Settings—Git.

• Create or Edit Ignore File If you bind a project to Git outside of Flare (i.e., you do not use Flare's interface to do the binding), you should make sure that you have a .gitignore file. You can add the .gitignore file by selecting an option in the Source Control Explorer or Project Properties dialog. Once you have a project containing a .gitignore file, the button in the interface changes to "Edit Ignore File," so that you can open the file to make edits to it. See Adding and Editing an Ignore File.

If Using Perforce Helix Core

• Bind If you want to add your project to source control so other users can access it, you need to connect the project to your source control tool. This process is called "binding" the project to source control. See Binding a Project to Perforce Helix Core.
• Unbind Provider If you no longer need your project connected to source control, you can remove the connection by "unbinding" the provider. See Unbinding a Perforce Helix Core Provider.

• Disable Provider If you do not want to see the source control interface elements in Flare, you can disable the provider. This does not mean you cannot use source control. As long as the provider is still bound to the project, you can perform source control tasks in a third-party tool outside of Flare. See Disabling a Perforce Helix Core Provider.

• Import Project from Source Control If you have a project in Helix Core, you can import it to Flare so you can edit it. See Importing a Project From Source Control—Perforce Helix Core.
• View Pending Changes When you make changes to your project in Flare, you can see the files you have changed in the Pending Changes pane. You can also include or exclude changes if you do not want to submit all of your files at once. See Viewing Files That are Checked Out—Perforce Helix Core.
• Submit When you are finished working on a file, you can return it to source control. This overwrites the existing copy in source control and creates a backup of the file in the source control tool. See Submitting Source Control Files—Perforce Helix Core.

If Using Apache Subversion

• Bind This means to connect your project to Apache Subversion. After doing this, you can then take advantage of all the automated source control tasks (such as commit, revert, update, and so on). See Binding a Project to Subversion.
• Unbind Provider If you no longer need your project connected to source control, you can remove the connection by "unbinding" the provider. See Unbinding a Subversion Provider.

• Disable Provider If you do not want to see the source control interface elements in Flare, you can disable the provider. This does not mean you cannot use source control. As long as the provider is still bound to the project, you can perform source control tasks in a third-party tool outside of Flare. See Disabling a Subversion Provider.

• Import Project from Source Control If you have a project in Subversion, you can import it to Flare so you can edit it. See Importing a Project From Subversion.
• View Pending Changes When you make changes to your project in Flare, you can see the files you have changed in the Pending Changes pane. You can also include or exclude changes if you do not want to commit all of your files at once. See Viewing Modified Files—Subversion.
• Commit When you are finished editing files, you can commit them to source control. Committing a file overwrites the old copy of the file in the source control database with the new one from your local machine. So even if others will not be working on that file, it is a good idea to periodically commit files so that you have a backup in source control. See Committing Source Control Files—Subversion.
• Lock If you want to prevent other users from committing your files, you can lock the file. See Locking a File—Subversion.
• Unlock If you are finished working on a file and want to allow other users to commit it, you can unlock the file. See Unlocking a File—Subversion.
• View and Modify Network Settings You can view and modify your current source control network settings without having to close Flare. You can make changes to several settings, including SSL, HTTP proxy, and caching options. See Modifying Network Settings—Subversion.

If Using Microsoft Team Foundation Server

• Bind If you want to add your project to source control so other users can access it, you need to connect the project to your source control tool. This process is called "binding" the project to source control. See Binding a Project to Microsoft Team Foundation Server.
• Unbind Provider If you no longer need your project connected to source control, you can remove the connection by "unbinding" the provider. See Unbinding a Team Foundation Server Provider.

• Disable Provider If you do not want to see the source control interface elements in Flare, you can disable the provider. This does not mean you cannot use source control. As long as the provider is still bound to the project, you can perform source control tasks in a third-party tool outside of Flare. See Disabling a Team Foundation Server Provider.

• Import Project from Source Control If you have a project in Team Foundation Server, you can import it to Flare so you can edit it. See Importing a Project From Team Foundation Server.
• View Pending Changes When you make changes to your project in Flare, you can see the files you have changed in the Pending Changes pane. You can also include or exclude changes if you do not want to check in all of your files at once. See Viewing Files That are Checked Out—Team Foundation Server.
• Check In When you are finished working on a file, you can check it in it to source control. This overwrites the existing copy in source control and creates a backup of the file in the source control tool. See Checking In Source Control Files—Team Foundation Server.
• Undo Check Out If you do not want to keep changes to a file, you can undo the check out. and restore the file to the state it was in the last time it was checked into source control. See Undoing a Checkout of Source Control Files—Team Foundation Server.

Navigation

Home Page View

Branches View

Pending Changes View

Settings View