You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
improvement(lanes): fetch updates from main when on a lane (teambit#6158)
- when running `bit import`, fetch lane-components not only from lane-scope but also from original scope.
- when running `bit status`, show how many snaps the main is ahead.
- when running `bit status` and there are issues getting the diverge-data, show them to the user.
- improve `bit status --json` to show the staged versions.
- fix components with multiple parents in the history to show the staged versions correctly.
Copy file name to clipboardExpand all lines: scopes/lanes/lanes/lanes.docs.mdx
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -87,6 +87,12 @@ Summary of when/what lanes data is saved per command:
87
87
- in case the merge wasn't done and the user is trying to export, the remote blocks is as it finds out that its head doesn't exist on the incoming component.
88
88
- in case the snap-merge failed due to a conflict, it saves the conflict and heads data into `.bit/unmerged.json` file.
89
89
90
+
### Merge components
91
+
92
+
- to merge an entire lane, use `bit lane merge`.
93
+
- to get updates from a remote lane, run `bit import`, and then `bit checkout head`. alternatively, run `bit merge <component-id>` in one command.
94
+
- to merge an individual component from a lane to main, run `bit lane merge <lane> --pattern <component-id>` when on main.
95
+
90
96
### Useful APIs
91
97
92
98
- bit-map `getAllIdsAvailableOnLane()` filters the currently checked out lane.
0 commit comments