Skip to main content Skip to complementary content

Creating a local branch from Talend Studio

About this task

When working on a Git managed project, you can create local branches from within your Talend Studio and keep your changes local until you push them to the Git server.

Your Talend Studio provides two options for you to create a local branch:
  • Creating a new branch based on a selected source
  • Checking out a remote branch as a local one
Information noteNote: In the context of Git branching, main or master can be regarded as a special branch.

After the branch is created, you can work on it and manage it using tools provided by your Talend Studio.

Creating a new branch based on a selected source

Procedure

  1. From the Talend Studio, click the top bar of the Repository tree view and select New Branch from the drop-down menu.
    Repository tree view.
  2. In the New Branch dialog box, select the source, which can be a remote or local branch your local branch will be based on, enter a name for your new branch, and click OK.
    New Branch dialog box.
  3. When asked whether to switch to the newly created branch directly, click OK to switch or click Cancel to stay on the current branch.

Checking out a remote branch as a local one

Procedure

  1. Click the top bar of the Repository tree view in Talend Studio.
  2. From the drop-down menu, select a remote branch which you want to check out as a local one, and then select check out as local branch from the sub-menu.

    There are at most ten remote branches displayed in the drop-down menu. If the remote branch you want to check out is not in the drop-down menu, click > Click for more remote branches ... and in the Remote branches dialog box displayed, select the target branch and click Checkout as local.

    Repository tree view.
  3. In the Checkout as local branch dialog box, enter a name for your new branch, and click OK to create the branch and switch to it.
    Checkout as local branch dialog box.

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!