Skip to main content

Adding and removing components

The basket is filled from the component grid, and (once a deployment is open) the Deployment tab itself has an Add button that pulls from several different sources.

Add to the basket from a component tab​

  1. Open a category from Data Components or Object Components.
  2. Select one or more rows.
  3. Toolbar Add to Basket (or right-click → Add to Basket, or Ctrl+B).

The Basket column lights up on each added row.

Remove from the basket​

In any component tab, category or basket:

  • Toolbar Remove from Basket (Ctrl+Shift+B).
  • Right-click → Remove from Basket.

Or, in basket mode:

  • Delete removes the selected rows from the basket (not from the workspace).
  • Toolbar Empty Basket (right-click → Empty Basket) clears everything.

Add to a deployment from the Deployment tab​

The Deployment tab's toolbar has an Add button (also Add Components... on the right-click menu). It opens Add Components to Deployment, whose Add Method picks where the components come from:

  • From the file system. Pick file(s).
  • From the basket. Pull in whatever's currently staged.
  • From a branch. Every component changed on the current branch compared to its base.
  • From a commit. Every component touched by a specific commit.
  • From a date range. Every component changed between two dates.
  • From a task ID. Every component associated with a tracked task.
  • DataChangesets. Every changeset a work item keeps in the workspace, each pinned to its latest committed version. The work item box starts with the active task.

The available options depend on the workspace's version-control and task-tracking connections.

Adding many components​

An add runs under a busy overlay with a Cancel button. Cancelling, even while version control is still being read, changes nothing: items already in the deployment are moved or removed only once the add goes ahead.

An add that would bring in more than 200 new items asks first, in Add Many Items: This adds {n} items from {c} categories to the deployment file. That is a lot to review. Add them all?. Add All (with the number of items) goes ahead; Cancel leaves the deployment as it was. A release whose commits touched that many files is more often a merge, a reformat or the wrong branch than a deployment anyone meant to review row by row.

Undo takes back the whole add: the rows it added, and the items it moved to a newer commit go back to the commit they were at.

What's next​

Last updated on