Skip to content

ci: restore --keep-lane in bit_pr #10586

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
GiladShoham merged 2 commits into from
Aug 9, 2026
+8 −7
Merged

ci: restore --keep-lane in bit_pr #10586

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8bea7d8
ci: restore --keep-lane in bit_pr
zkochan Aug 8, 2026
876addd
Merge branch 'master' into restore-keep-lane
github-actions[bot] Aug 9, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 8 additions & 7 deletions .circleci/config.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -856,13 +856,14 @@ jobs:
# NOTE: PR builds run the FULL pipeline by default. To trade specific tasks for speed on a
# given PR (no YAML change needed), add a `[skip-tasks: <names>]` token to the commit
# message, e.g. `[skip-tasks: ExtractSchema,GeneratePreview,GenerateEnvTemplate,PublishComponents]`.
# No --keep-lane: the reusing flow serves components unchanged since an earlier export
# from the lane, with artifacts built from older commits of the branch. Capsules then mix
# generations of @teambit packages and cross-copy `instanceof` breaks in capsule spec
# runs - on a PR that snaps core components (so their specs actually run), bit_pr fails
# deterministically from the second push onward. The temp-lane flow rebuilds every run
# from one commit, trading the lane's persistent history on Bit Cloud for correctness.
command: 'cd bit && bit ci pr --build --skip-cleanup'
# --keep-lane: reuse the lane named after the branch across pushes, so the PR keeps one
# lane on Bit Cloud and pushes only re-snap what actually changed. Known hazard while
# #10583 is open: the reusing flow serves components unchanged since an earlier export
# with artifacts built from older commits, so capsules can mix generations of @teambit
# packages and cross-copy `instanceof` breaks in capsule spec runs. If a PR that snaps
# core components starts failing from the second push onward, that is this - rename the
# branch (fresh lane) or drop --keep-lane on that PR.
command: 'cd bit && bit ci pr --build --keep-lane --skip-cleanup'
Comment thread
qodo-free-for-open-source-projects[bot] marked this conversation as resolved.
no_output_timeout: '50m'
environment:
NODE_OPTIONS: --max-old-space-size=30000
Expand Down