Component Status

Bit workspaces help you track component changes during development. Using the bit status command, you can see the current state of each component in your workspace:

$ bit status
Copied

Understanding the workspace status helps you determine the next steps for sharing your components:

No components have pending changes. Either no files are tracked in the workspace, or the tracked components have no pending changes.

$ bit status

nothing to tag or export
Copied

Components you've created but not yet tagged.

$ bit status

new components
 (use "bit tag --all [version]" to lock a version with all your changes)

 > ui/login ... ok
Copied

Use bit tag to tag all new components with a version. Then, use bit export to share them. Example:

$ bit tag --message "releasing new components"
$ bit export
Copied

Components tagged and ready to be shared.

$ bit status
staged components
 (use "bit export <remote_collection> to push these components to a remote Collection")

 > string/index. versions: 0.0.1, 0.0.2, 0.0.3 ... ok
 > string/is-string. versions: 0.0.1 ... ok
 > string/pad-left. versions: 0.0.1, 0.0.2 ... ok
Copied

To export staged components, use bit export:

$ bit export
Copied

Components with changes since their last snap. Review changes with bit diff <component-id>.

bit status
Copied

modified components
 (use "bit tag --all [version]" to lock a version with all your changes)
 (use "bit diff" to compare changes)

> string/pad-left ... ok
Copied

To share these changes, it is recommended to use a lane:

$ bit lane create proposing-changes
$ bit snap --message "updated pad-left"
$ bit export
Copied

Newer versions of these components are available.

$ bit status

pending updates
 (use "bit checkout [version] [component_id]" to merge changes)
 (use "bit diff [component_id] [new_version]" to compare changes)
 (use "bit log [component_id]" to list all available versions)

 > string/pad-left current: 0.0.1 latest: 0.0.2
Copied

You can choose to checkout the new version using bit checkout head.

Components deleted locally or remotely.

$ bit status

components deleted
(tag/snap and export the components to update the deletion to the remote. to undo deletion, run "bit recover")

 > ui/login ... ok
Copied

Use bit export to apply the component deletion in your remote scope.

These components depend on modified components. They will be automatically staged when their dependencies are tagged with a new version.

$ bit status

components pending to be tagged automatically (when their dependencies are tagged)
 > pages/homepage ... ok
Copied