Building Lanes

Lanes provide a mechanism to implement modifications across a group of components, facilitating the process of reviewing these changes and ensuring their atomic release, and the update of dependent components.

If you are using Git, you can simply create a branch (using git branch), and submit a PR using our various CI scripts. Skip to Submit change request.

Create a new lane

Run the following command to create a new lane:

$bit
Copiedcopy

The output should confirm that the lane was created successfully, and that your workspace is now on that lane:

successfully added and checked out to a new lane my-lane

Import the components to modify

Modify the components available in your workspace or import new ones. You can also create new components which will be available only on that lane, until it is merged to 'main'.

For example, import the following component and modify its source files, dependencies, and configuration:

$bit
Copiedcopy

Note that components can be modified in a lane even if you only have read permissions to their scopes. Changes made to components in a lane will not be reflected in their scopes until the lane is merged to main, by a user with write permissions to the components' scopes.

Snap component changes

Run the following to snap the modified components:

$bit
Copiedcopy

Run the following to export the new lane with the new snaps:

$bit
Copiedcopy

The new snaps are contained in a lane and hosted in the lane's remote scope.


After exporting, make sure to checkout your build status, and iterate to make sure build are properly passing on Ripple CI or your CI of choice.

For more specific information on Lanes, and helpful examples check out:

What's next?