![]() ![]() For each commit, the list shows the commit message, the author, and the commit timestamp. This area shows a list of all commits made to the selected branch, or to all branches. You can select multiple branches to delete them in a batch. Push outgoing commits to the selected branch. You can select multiple branches to update them in a batch. This is equivalent to running git rebase with the selected branch name.įetch changes from the selected branch and rebase the current branch on top of these changes.įetch changes from the selected branch and merge them into the current branch. Rebase the current branch on top of the selected one. Rebase a branch on top of the current branch.Ĭompare the selected branch with the branch that is currently checked out.Ĭompare the selected branch with the local state of the branch that is currently checked out. Branches pane toolbarĬreate a new branch based on the selected branch. The Branches pane lists all local and remote branches, and lets you perform all branch operations. The Commit Details pane is located on the right under the Changed Files pane and shows the details of the selected commit. The Changed Files pane is located on the right of the tool window and shows the list of files that were modified within the selected commit. The Commits pane is located in the central part of the tool window and shows the commits to all or to the selected branches. From this pane, you can switch between branches, create new branches and delete the ones you don't need anymore, filter the log by branch, and more. The Branches pane is located on the left and shows all local and remote branches. To assign a custom shortcut, go to Settings | Keymap | Version Control Systems and search for the Show VCS Log action. This tab shows all local and remote branches, and all changes committed to all branches, or to a specific branch or repository. Because you control the regular expression, you can control exactly what this looks like.įor more information about Git hooks in general, see the Git documentation.This tab is only available if you are using Git or Mercurial for version control. ![]() This text can appear in-line with other text or in a more formal form-style layout. These regular expressions are case-insensitive and you must identify the review ID portion with parenthesis: Text Here are some common ways of specifying the review ID and the corresponding regular expressions. The regular expression is specified using the -review-id-regex hook command option. You will need to supply a Java-style regular expression that identifies this text and specifically calls out the review ID inside that text. The format of this text is completely up to you. To use the ensure-review-started and ensure-reviewed hooks, you must require developers to put the review ID somewhere in the Git commit message. Specify Java-style regular expressions to map changelists uploaded from our client tools to this Git server: The Client Configuration Mapping section defines correspondence between files uploaded by the various Collaborator clients and this server-side Git configuration. For example, you might need to generate and/or accept trust certificates and so forth. If enabled, this feature lets users select committed revisions to review directly from the web browser, without having to install any client programs.įull path to the Git command line client ( git.exe).Ĭlick Test Connection to verify that the connection between Collaborator server and your Git server is established successfully and is trusted. When a version control server entry is created automatically, this is filled in with Git. The title is displayed to users, so it should be something that everyone will understand, even if they are going through proxies, VPNs, or other such things. ![]()
0 Comments
Leave a Reply. |