Skip to main content Skip to complementary content
Close announcements banner

Creating a tag for a project

For a Git managed project, a tag is a read-only copy that records the current state of the project at the point of time the tag is created.

Information noteTip: When working in a tag, you can make changes to your project items, but you will be unable to permanently save your changes to an item unless you copy the item to a branch. For how to copy an item to a branch, see Copying items from a branch or a tag.

About this task

The following procedure describes how to create a tag for a project in Talend Studio.

If you are working on a project managed by Talend Administration Center, you can also create a tag in Talend Administration Center. For more information, see How to manage Git tags.

Information noteNote:
  • Close all open editors in the design workspace before trying to create a tag. Otherwise, a warning message will appear prompting you to close all open editors.
  • All tags are visible for all projects on the same Git repository. Therefore, if you create some tags for one project, all other projects on the same Git repository will have the same list.

Procedure

  1. Open the remote project for which you want to create a tag.
  2. Click the top bar of the Repository tree view to open a drop-down menu.
  3. Select More ... from the drop-down menu and then select Add Tag from the sub-menu.
  4. In the New Tag dialog box, select the source, which can be the main or a branch based on which your tag will be created, enter a name for your new tag, and click OK.
    Information noteWarning: You cannot create tags based on a local branch you have created in Talend Studio.
    Creating a tag may take some time. When done, the tag you created will be listed on the drop-down menu when clicking the top bar of the Repository tree view, and you can switch to it by following the steps in Switching between branches or tags.

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 – let us know how we can improve!