#GIT BLAME COMMIT NUMBER FULL#

Review a project's snapshot at a specific revision To customize the date format, go to Settings | Appearance and Behavior | System Settings | Date Formats.įor more details on the Log tab of the Git tool window Alt+9, see Log tab. To avoid setting filters back and forth, click on the toolbar to open a new tab matching your filters. Switch the focus to the search field by pressing Ctrl+L. This is especially useful if you have commits to different repositories and multiple branches all mixed in the Log tab of the Git tool window Alt+9.

Press the Left and Right keys to jump to the parent/child commit.

#GIT BLAME COMMIT NUMBER FULL#

Search through the list of commits by entering full commit names or messages or their fragments, revision numbers, or regular expressions.įilter the commits by branch or favorite branches, user, date, and folder (or root and folder for multi-root projects).Ĭlick the Go to Hash/Branch/Tag icon on the toolbar or press Ctrl+F and specify a commit hash, tag or the name of a branch you want to jump to (you will be taken to the latest commit in that branch).Ĭlick an arrow to jump to the next commit in a long branch: Hover the mouse cursor over the colored stripe to invoke a tip that shows the root path: Navigate and search through project history In multi-repository projects, the colored stripe on the left indicates which root the selected commit belongs to (each root is marked with its own color). It shows all changes committed to all branches and remote repositories: To view project history, open the Log tab of the Git tool window Alt+9. You can review all changes made to a project sources that match the specified filters. This helps you locate the author of any change, review the differences between file versions or commits, and safely roll back and undo changes if necessary. In PhpStorm, you can trace back all changes in your project>.

Git blame commit number