Projects & Files

Pipelines, documents, and custom components all live together in one file tree per workspace. Organize them into folders the way you would files in a code editor.

Folders and tabs

Right-click a folder, pipeline, or document to rename, move, duplicate, or delete it. Opening an item adds a tab to the tab strip along the top of the editor. Tabs stay open, and keep their unsaved changes, as you switch between them, so you can go back and forth between a pipeline and the component it calls.

Version history

Each pipeline has a Version history panel.

• Publish saves the current draft as a version. Environments promote published versions, so nothing reaches an environment until you publish it.
• Compare shows what changed between two versions, or between a version and your current draft: steps and lines added, removed, or changed.
• Restore replaces the canvas with a version's steps. Undo brings back what was there before.

When you restore, Pipeloom checks what that version uses:

• If a source, destination or sync it names no longer exists, it lists them. You can restore anyway, but those steps point at nothing, and the pipeline can't be deployed until you remove them or point them somewhere else.
• If a sync's streams have changed since that version was published, it shows what changed. Tick a sync to put its streams back as they were: which streams are selected, and each stream's sync mode, write mode, cursor and primary key.

Internal history vs. Git Sync

Pipeloom keeps two kinds of history, and both use git:

• Internal history is saved automatically in the background every time you save. It doesn't push anywhere, and there's nothing to set up. It's what the platform uses to keep a history of everything in your workspace.
• Git Sync is a one-way export that you set up. It pushes content you've promoted to an environment to a repository you own, so your pipelines go through your own review process alongside your own code. It's not a live two-way sync.

To get your pipelines into your team's GitHub, use Git Sync. To see or bring back an earlier version of a pipeline, use its version history.