Skip to main content Skip to complementary content

Viewing the Git commit history

You can view the commit history of your project or an item like Job, Joblet, Route, and Routelet specific to the current branch or tag from your Talend Studio.

Procedure

  1. Switch to the branch or tag.
    For more information, see Switching between branches or tags.
  2. To view the commit history of your project, click the top bar of the Repository tree view and select History from the drop-down menu to open the Git History view.
    You can also open the Git History view by:
    • selecting Window > Show view from the Talend Studio menu and then in the Show View dialog box, selecting Talend > Git History and clicking OK.
    • clicking the History button in the Talend Git Staging view.
  3. To view the commit history of a specific item like Job, Joblet, Route, and Routelet, select the item in the Repository tree view and click Git > History in the context menu to open the Git History view.
  4. In the Git History view, select any commit record to view its details.
    Git History view.

    You can switch between the history of the project and the selected item in the Repository by clicking the All and the <item name> tabs on the top of the Git History view.

    In the upper right corner of the Git History view, you can click Current branch or All branches to view the history of the current branch or all branches. You can also find commits by clicking the down arrow next to the Find field, selecting a type like Id, Author, or Branch/Tag from the drop-down menu, and then entering the search keyword in the Find field.

    In the Git History view, you can create a branch from a commit by right-clicking the commit and click Checkout as branch in the contextual menu. In the Checkout as a Branch dialog box, enter a name for your new branch, and click OK. When asked whether to switch to the newly created branch directly, click OK to switch or click Cancel to stay on the current branch.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!