Pushing changes on a local branch to the remote end - Cloud - 8.0

Talend Data Fabric Studio User Guide
Version
Cloud
8.0
Language
English (United States)
EnrichDitaval
Data Fabric
Product
Talend Data Fabric
Module
Talend Studio
Content
Design and Development

About this task

When working on a local branch of a Git managed project, your changes are automatically committed to your local repository when they are saved. However, they are not automatically pushed to the Git server - you need to push them manually using the Git Push tool provided within your Talend Studio.

Warning: If you created your local branch on a project that has referenced projects and if you have the project references management right, the project reference relationships will be automatically created for your branch on the remote repository when you push your branch for the first time. If you don't have the project references management right, you will need to ask your administrator to set up the project references manually in the Talend Administration Center.

For more information about referenced projects, see Working with referenced projects.

Procedure

  1. Save your changes so that they are committed to your local repository.
  2. Optionally, update your local Git repository to prevent possible errors caused by asynchronization between your local Git repository and the server.
    For more information, see Updating a local branch.

    When you profile databases related to analyses and reports, this step is mandatory. As each table has its own ID, when you are multiple users working on the same table locally, you may encounter conflicts when you merge branches.

  3. Click the top bar of the Repository tree view and select Push from the drop-down menu.
  4. If any editor windows are open, you will see a warning message. Click OK to close the editor windows and proceed with the push action.
    • If the push operation is not complete within 1.5 seconds, a dialog box pops up to indicate the push progress. You can:
      • Click Run in Background to close this dialog box to keep the progress information shown only at the lower right corner.
      • Click Cancel to cancel the push operation and close the dialog box.
    • This dialog box closes automatically when the push operation is complete or any conflict occurs. For more information about conflict handling, see Resolving conflicts between branches.
  5. If a Push Rejected by Server dialog box pops up indicating a push failure, either:
    • Click Yes to let the Studio update your local Git repository and then push your changes again automatically.
    • Click No if you want to stop the push action, update your local Git repository and then push your changes again manually.
  6. When the push operation completes, a dialog box opens informing you that your changes have been pushed to the Git server successfully. Click OK to close the dialog box.

Results

Your changes have now been pushed to the Git server. If this is the first push from your local branch, a remote branch with the same name is automatically created as the associated branch to hold the commits you push from your local branch.