You can also paste hashes into here.įorward/back buttons, row number. Very useful for copy/paste into a terminal to perform an action on a given commit you used gitk to find. In the context menu for a branch, we have git-checkout and the -d (delete) mode of git-branch. The "mark a commit" and related commands should be self-explanatory at this point. Longer description on the man page, but of course you have to understand the concept of the index to really get it. git-reset (reset branch to here) This prompts you for soft, mixed, or hard, with a brief reminder of what each does.git-diff-tree (write commit to file, rarely used).Listing them will at least help you find the right documentation to understand what they do, if you don't already! This presents several common git porcelain commands, generally in a common/default mode of operation. There's a list of keybindings here! Sweet. If you've looked at git-log before, you'll have seen a lot of this. The man page is an excellent place to find more information about the ways you can control views (it's mostly in the commit limiting section). These can also be set interactively in the "view" menu. You can reread them, and list to click a particular one to show it in the history.Īs the man page says, gitk takes git-rev-list options to help specify what history should be shown. References include tags and branches (which may be remote). This is an excellent thing to use if you're rebasing and want to make sure you didn't mess up - you can see both the original and rebased versions. Update, on the other hand, refreshes all the information, but still shows all commits that were previously shown. This means if a branch has been removed/rebased, if some commits are now dangling, you don't see them anymore. Reload refreshes everything as if you started the program over with the same configuration. Update and reload: This is probably the most confusing thing. This has changed somewhat over the last few major versions - I'm describing the current state. ![]() Knowing the commands that are behind everything (or at least generally equivalent) helps learn to use command-line tools more easily, and also shows you where to look in documentation to understand gitk better! File menu Here's a stab at it, from a "how does it work" point of view. I've never seen anything specifically for gitk.
0 Comments
Leave a Reply. |