This is similar to Walk Behavior → Compressed Graph, but only for selected revisions.Ĭollapsed items are displayed in the graph with hollow circles and squares. Collapse revisionsĭo not show parent commits up to a merge or branch point or a commit marked with a branch or tag. Edit notesĮdit notes of the selected commit. To abandon the reverted changes, perform a hard reset. You may choose to commit immediately or edit and commit later. All changes are integrated into your working tree. Revert changes from which were made in the selected revision. the section called “Exporting a Git Working Tree”). This brings up a dialog for you to confirm the revision, and select a location for the export (cf. Export this version.Įxport the selected revision to an archive file such as zip. Rebase current branch on top of the selected commit (cf. Create tag from revisionĬreate a tag on a selected revision (cf. Create branch from revisionĬreate a branch based on the selected revision (cf. Useful if you want to have your working tree reflect a time in the past, or if there have been further commits to the repository and you want to update your working tree one step at a time. Update your working tree to the selected revision. Resets the HEAD to the selected commit (cf. the section called “The Repository Browser”). Open the repository browser to examine the selected file or folder in the repository as it was at the selected revision (cf. For folders this option will first show the changed files dialog allowing you to select files to compare. This works in a similar manner to comparing with your working tree. Compare with previous revisionĬompare the selected revision with the previous revision. It is harder to read than a visual file compare, but will show all file changes together in a compact format. This shows only the differences with a few lines of context. View the changes made in the selected revision as a Unified-Diff file (GNU patch format). If the log dialog is for a folder, this will show you a list of changed files, and allow you to review the changes made to each file individually. The default Diff-Tool is TortoiseGitMerge which is supplied with TortoiseGit. the section called “TortoiseGit Dialog Settings”).Ĭompare the selected revision with your working tree. Also, the labels can be configured to be a the right side of the commit message or the displayed text to contain the whole of the commit message (cf. the section called “TortoiseGit color Settings 2”). There are also rectangles to indicate the bad versions (light red) on bisecting, blue for known good and gray for skip.ĭepending on what branch/tag label you open the context menu, it is optimized for that ref it was opened on (e.g., a local branch offers directly to switch to it and to push it whereas a remote branch has no push option). The boxes with rounded corners for remote tracking branches are used to indicate which of (possible several remote branches) is the corresponding remote tracking branch (e.g., master and origin/master). The boxes with rounded corners for local branches indicate that it has an associated remote tracking. The active branch is displayed as a dark red rectangle (by default), the green ones are local branches and the peach ones are remote branches. Normally branches are displayed as normal rectangles. The annotated ones have an apex at the right side. In Git there are two tag types: normal tags and annotated tags. Tags are by default displayed as yellow rectangles. Commits which have an associated reference are decorated with a label. In this column the subjects of the commits are shown. Also, because it is so clearly a remote and read-only action, there is no possibility of goofing up local state or committing new work to the wrong branch.Commit messages and branch/tag indicators It can be much easier to hone in on a state or change of interest by clicking around or using GitHub’s search features. GitHub’s hyperlink-rich presentation of your repo and its history is one of the top reasons to sync local work to a copy on GitHub, even if you keep it private. You generally have to checkout these previous states, which raises the prospect of getting comfortable in the “detached head” state and unintentionally making new commits on the wrong branch or on no branch at all. Yes, technically, you can visit past states of your project using Git commands locally. The ability to quickly explore different commits/states, switch between branches, inspect individual files, and see the discussion in linked issues is incredibly powerful. This is where GitHub (and GitLab or BitBucket) really shine.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |