Skip to main content
A branch may contain a large number of pipelines, which by default are listed alphabetically in the Files panel. To organize pipelines in a branch, you can arrange them into named folders. Folders can be nested inside folders, up to 10 levels deep, to create a structure that makes sense to you and your team. Pipeline names must be unique within a folder but can be duplicated in different folders.

Create a folder

To create a top-level folder:
  1. Click Files at the top of the canvas.
  2. Click the + icon in the Files panel, then click Folder.
  3. Enter a name for the folder. Folder names can contain alphanumeric characters, dashes, and underscores.
  4. Click Create.
To collapse or expand a folder, click the > icon next to it.

Manage folders

Hover over a folder in the Files panel and click the three dots … next to its name to open its context menu. From the context menu, you can:
  • Add a pipeline to the folder, or add another folder as a subfolder.
  • Rename the folder.
  • Copy the folder. Read Copying pipeline folders.
  • Paste a copied pipeline or folder into the folder.
  • Delete the folder. All the pipelines and subfolders it contains are also deleted, and this can’t be undone. However, active schedules for pipelines in a deleted folder will continue to use the latest published version of the pipelines.
To move a pipeline between folders, or between root and folder, drag and drop it. You can’t move a pipeline to a folder where another pipeline with the same name already exists, and attempting to do so results in a warning notice.
Be aware of the following when working with pipeline folders:
  • Moving a pipeline into a different folder will break other pipelines that reference it via Run Orchestration or Run Transformation components. You will therefore need to update any pipelines that reference the moved pipeline.
  • Renaming a folder will also break pipelines that reference a pipeline contained in the folder you have renamed. You will need to update any pipelines that reference pipelines in the renamed folder.
  • Any existing schedules that use the moved pipeline will not be updated. The pipelines will have to be republished and the schedule recreated.
  • Empty folders cannot be committed to Git. These remain on your local branch, but aren’t committed until they contain at least one file.
  • Moving a pipeline to a different folder is considered a change to your branch, and therefore needs to be committed to Git.

Copying pipeline folders

To make a copy of a pipeline folder and all of its contents, including pipelines and subfolders, do one of the following:
  • Click the pipeline folder to select it, then press ctrl + c (Windows) or cmd + c (Mac) to copy it.
  • Hover over the pipeline folder, click the three dots … that appear next to it, and click Copy.
Then do one of the following:
  • Click the folder in which you want to paste a copy of the pipeline folder, then press ctrl + v (Windows) or cmd + v (Mac) to paste it.
  • Hover over the folder in which you want to paste a copy of the pipeline folder, click the three dots … that appear next to it, and click Paste.
If you make a copy of a pipeline folder in the same place as the original folder, the new pipeline folder will be called _copy_your-folder-name. Any additional copies will be called _copy_your-folder-name_2, ..._3, and so on.The names of any pipelines and subfolders in the copied folder are not changed.