Manage lanes - if no sub-command is used, runs "bit lane list"
$bit lane [sub-command]
Copiedcopy
$bit l [sub-command]
Copiedcopy

Options

OptionOption AliasDescriptionValue Type
--details-dshow more details on the state of each component in each laneboolean
--json-jshow lanes details in json formatboolean
--remote-rshow all remote lanes from the specified scopestring
--merged-list only merged lanesboolean
--not-merged-list only lanes that haven't been mergedboolean

list

list local or remote lanes

$bit lane list
Copiedcopy

Options

OptionOption AliasDescriptionValue Type
--details-dshow more details on the state of each component in each laneboolean
--json-jshow lanes' details in a json formatboolean
--remote-rshow all remote lanes from the specified scopestring
--merged-list only merged lanesboolean
--not-merged-list only lanes that haven't been mergedboolean

switch

switch to the specified lane

$bit lane switch <lane>
Copiedcopy

Options

OptionOption AliasDescriptionValue Type
--head-hswitch to the head of the lane/main (fetches the latest changes from the remote)boolean
--auto-merge-resolve-rmerge local changes with the checked out version. strategy should be "theirs", "ours" or "manual"string
--get-all-aDEPRECATED. this is currently the default behaviorboolean
--workspace-only-checkout only the components in the workspace to the selected laneboolean
--skip-dependency-installation-xdo not install dependencies of the imported componentsboolean
--pattern-pswitch only the lane components matching the specified component-pattern. only works when the workspace is empty component name, component id, or component pattern. use component pattern to select multiple components. wrap the pattern with quotes. use comma to separate patterns and "!" to exclude. e.g. "ui/**, !ui/button". use '$' prefix to filter by states/attributes, e.g. '$deprecated', '$modified' or '$env:teambit.react/react'. use `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern.string
--alias-nrelevant when the specified lane is a remote lane. create a local alias for the lane (doesnt affect the lane's name on the remotestring
--json-jreturn the output as JSONboolean

show

show lane details. if no lane specified, show the current lane

$bit lane show [lane-name]
Copiedcopy

Options

OptionOption AliasDescriptionValue Type
--json-jshow the lane details in json formatboolean
--remote-rshow details of the remote head of the provided laneboolean

create

creates a new lane and switches to it

$bit lane create <lane-name>
Copiedcopy

Options

OptionOption AliasDescriptionValue Type
--scope-sremote scope to which this lane will be exported, default to the workspace.json's defaultScope (can be changed up to first export of the lane with "bit lane change-scope")string
--remote-scope-DEPRECATED. use --scopestring
--alias-a local alias to refer to this lane, defaults to the `<lane-name>` (can be added later with "bit lane alias")string
--fork-lane-new-scope-create the new lane in a different scope than its parent lane (if created from another lane)boolean

remove

remove or delete lanes

$bit lane remove <lanes...>
Copiedcopy

Options

OptionOption AliasDescriptionValue Type
--remote-rdelete a remote lane. use remote/lane-id syntax e.g. bit lane remove owner.org/my-lane --remote. Delete is immediate, no export requiredboolean
--force-fremoves/deletes the lane even when the lane is not yet merged to mainboolean
--silent-sskip confirmationboolean

change-scope

changes the remote scope of a lane

$bit lane change-scope <remote-scope-name>
Copiedcopy

Options

OptionOption AliasDescriptionValue Type
--lane-name-lthe name of the lane to change its remote scope. if not specified, the current lane is usedstring

alias

adds an alias to a lane

$bit lane alias <lane-name> <alias>
Copiedcopy

rename

EXPERIMENTAL. change the lane-name locally

$bit lane rename <new-name>
Copiedcopy

Options

OptionOption AliasDescriptionValue Type
--lane-name-lthe name of the lane to rename. if not specified, the current lane is usedstring

diff

show diff between lanes

$bit lane diff [values...]
Copiedcopy

Options

OptionOption AliasDescriptionValue Type
--pattern-show lane-diff for components conforming to the specified component-pattern only component-pattern format: component name, component id, or component pattern. use component pattern to select multiple components. wrap the pattern with quotes. use comma to separate patterns and "!" to exclude. e.g. "ui/**, !ui/button". use '$' prefix to filter by states/attributes, e.g. '$deprecated', '$modified' or '$env:teambit.react/react'. use `bit pattern --help` to understand patterns better and `bit pattern <pattern>` to validate the pattern.string

add-readme

EXPERIMENTAL. sets an existing component as the readme of a lane

$bit lane add-readme <component-name> [lane-name]
Copiedcopy

remove-readme

EXPERIMENTAL. remove lane readme component

$bit lane remove-readme [laneName]
Copiedcopy

import

import a remote lane to your workspace and switch to that lane

$bit lane import <lane>
Copiedcopy

Options

OptionOption AliasDescriptionValue Type
--skip-dependency-installation-xdo not install dependencies of the imported componentsboolean
--pattern-pimport only components from the lane that fit the specified component-pattern to the workspace. works only when the workspace is emptystring

remove-comp

DEPRECATED. remove components when on a lane

$bit lane remove-comp <component-pattern>
Copiedcopy

Options

OptionOption AliasDescriptionValue Type
--workspace-only-do not mark the components as removed from the lane. instead, remove them from the workspace onlyboolean
--update-main-EXPERIMENTAL. remove, i.e. delete, component/s on the main lane after merging this lane into mainboolean

fetch

fetch component objects from lanes. if no lane-id is provided, it fetches from the current lane

$bit lane fetch [lane-id]
Copiedcopy

Options

OptionOption AliasDescriptionValue Type
--all-afetch all remote lanesboolean

eject

delete a component from the lane and install it as a package from main

$bit lane eject <component-pattern>
Copiedcopy

merge

merge a local or a remote lane to the current lane

$bit lane merge <lane> [pattern]
Copiedcopy

Options

OptionOption AliasDescriptionValue Type
--manual-same as "--auto-merge-resolve manual". in case of merge conflict, write the files with the conflict markersboolean
--auto-merge-resolve-rin case of a merge conflict, resolve according to the provided strategy: [ours, theirs, manual]string
--ours-DEPRECATED. use --auto-merge-resolve. in case of a conflict, keep local modificationsboolean
--theirs-DEPRECATED. use --auto-merge-resolve. in case of a conflict, override local with incoming changesboolean
--workspace-merge only lane components that are in the current workspaceboolean
--no-snap-do not auto snap after merge completed without conflictsboolean
--tag-auto-tag all lane components after merging into main (or tag-merge in case of snap-merge)boolean
--build-in case of snap during the merge, run the build-pipeline (similar to bit snap --build)boolean
--message-moverride the default message for the auto snapstring
--keep-readme-skip deleting the lane readme component after mergingboolean
--no-squash-relevant for merging lanes into main, which by default squashes all lane snapsboolean
--squash-EXPERIMENTAL. relevant for merging a lane into another non-main lane, which by default does not squashboolean
--ignore-config-changes-allow merging when components are modified due to config changes (such as dependencies) only and not filesboolean
--verbose-show details of components that were not merged successfullyboolean
--skip-dependency-installation-xdo not install dependencies of the imported componentsboolean
--skip-fetch-use the local state of target-lane if exits locally, without updating it from the remoteboolean
--include-deps-relevant for "--pattern" and "--workspace". merge also dependencies of the specified componentsboolean
--resolve-unrelated-relevant when a component on a lane and the component on main have nothing in common. merge-strategy can be "ours" (default) or "theirs"string
--include-non-lane-comps-DEPRECATED (this is now the default). when merging main, include workspace components that are not on the lane (by default only lane components are merged)boolean
--exclude-non-lane-comps-when merging main into a lane, exclude workspace components that are not on the lane (by default all workspace components are merged)boolean

merge-abort

abort the recent lane-merge. revert the lane object and checkout accordingly

$bit lane merge-abort
Copiedcopy

Options

OptionOption AliasDescriptionValue Type
--verbose-show details of components that didn't need to be mergedboolean
--silent-sskip confirmationboolean
--skip-dependency-installation-xdo not install packages of the imported componentsboolean

merge-move

EXPERIMENT. move the current merge state into a new lane. the current lane will be reset

$bit lane merge-move <new-lane-name>
Copiedcopy

Options

OptionOption AliasDescriptionValue Type
--scope-sremote scope to which this lane will be exported, default to the workspace.json's defaultScope (can be changed up to first export of the lane with "bit lane change-scope")string