feat(ci): add --skip-tasks flag + opt-in [skip-tasks] commit token to bit ci pr by davidfirst · Pull Request #10436 · teambit/bit

davidfirst · 2026-06-22T13:30:38Z

Adds a way to skip specific build/publish tasks on bit ci pr, reusing the builder's existing skipTasks mechanism (which reaches both the build pipeline and the snap/tag pipeline, so it covers schema/preview artifacts and publishing).

Skipping is opt-in. PR builds run the full pipeline by default — the schema/preview artifacts and publish are generally useful (browsable preview, API schema, installable lane packages). A developer who wants to trade specific tasks for speed on a single PR does so without touching the CircleCI YAML, two ways:

Commit-message token (primary): add [skip-tasks: GeneratePreview,ExtractSchema] to the commit message. bit ci pr parses it, merges it with any --skip-tasks flag, and strips the token from the snap message.
--skip-tasks <names> flag: general/user-facing, for explicit invocations.

Stacks on the --skip-cleanup work (#10431).

Tests:

Unit specs for the token parser (extractSkipTasksFromMessage) — list parsing, case-insensitivity, token stripping, edge cases.
e2e for both paths: a control run proves the tasks run by default (non-vacuous), then the flag and the commit-token are each asserted to omit them while a non-skipped sibling (PackComponents) confirms the pipeline still ran.

Exposes the existing builder skipTasks mechanism on `bit ci pr`, letting a PR build skip named build/publish tasks. On the throwaway PR lane the schema and preview artifacts and the npm publish aren't needed (they're regenerated on the final export to main), so skipping them speeds up the job. Wire bit_pr CI to skip ExtractSchema, GeneratePreview, GenerateEnvTemplate and PublishComponents (~8-10m). Flag is general/user-facing and reaches both the build and snap/tag pipelines.

qodo-free-for-open-source-projects · 2026-06-22T13:31:34Z

PR Summary by Qodo

feat(ci): add --skip-tasks to bit ci pr and speed up PR CI runs
✨ Enhancement ⚙️ Configuration changes 🧪 Tests 📝 Documentation 🕐 20-40 Minutes

Description

• Add --skip-tasks flag to bit ci pr to omit named build/publish tasks during snap/export.
• Propagate skipTasks through CI runtime and apply it in the CircleCI bit_pr job.
• Update CLI references and add e2e coverage for default vs skipped task execution.

Diagram

graph TD
  A["CircleCI bit_pr job"] --> B["bit ci pr --skip-tasks"] --> C["CiPrCmd"] --> D["CiMain"] --> E["Snap/Export pipeline"] --> F["Builder task filter"] --> G[("Bit Cloud / NPM")]

High-Level Assessment

The following are alternative approaches to this PR:

1. Parse/validate skip list early (array + known-task checks)

➕ Catches typos immediately (fail-fast) instead of silently not skipping
➕ Allows clearer help output (e.g., echo back normalized task ids)
➕ Easier to extend to repeated flags or structured config later
➖ Requires maintaining a source of truth for task names/aspect-ids
➖ More coupling between CLI layer and builder internals

2. Support repeated flags (`--skip-task X --skip-task Y`)

➕ More shell-friendly (no comma parsing/quoting issues)
➕ Easier to compose in CI templates and partial overrides
➖ Slightly larger CLI surface area
➖ Still needs internal parsing/merging logic

3. CI-only mechanism via env var or config file

➕ Avoids expanding the user-facing CLI surface if intended only for CI
➕ Centralizes CI tuning without changing command invocations
➖ Less discoverable; harder for users to leverage locally
➖ Adds another configuration channel to document and maintain

Recommendation: Current approach (a single --skip-tasks flag that plumbs through to existing skipTasks) is the best fit for this PR: it reuses proven builder behavior, improves CI speed immediately, and remains generally useful to end users. If follow-up work is planned, consider adding light validation/normalization of the skip list (and optionally a repeated-flag variant) to reduce typo-driven surprises.

Files changed (7) +86 / -11

Enhancement (2) +17 / -0

ci.main.runtime.tsPlumb 'skipTasks' through CI PR flows into pipeline execution +10/-0

Plumb 'skipTasks' through CI PR flows into pipeline execution

• Adds 'skipTasks' to the 'ci pr' runtime options and forwards it into both the existing-lane and temp-lane snap/export paths. Ensures the skip list reaches the underlying pipeline execution call that honors 'skipTasks'.

scopes/git/ci/ci.main.runtime.ts

pr.cmd.tsAdd '--skip-tasks' CLI option to 'bit ci pr' +7/-0

Add '--skip-tasks' CLI option to 'bit ci pr'
• Defines the new 'skip-tasks <tasks>' option (CSV of task names/aspect-ids) on the PR command. Passes the parsed value through to the CI runtime invocation.
scopes/git/ci/commands/pr.cmd.ts

Tests (1) +50 / -0

ci-commands.e2e.tsAdd e2e coverage for 'bit ci pr --skip-tasks' +50/-0

Add e2e coverage for 'bit ci pr --skip-tasks'

• Introduces an e2e scenario with a control run proving tasks execute by default, then a run with '--skip-tasks' asserting named tasks are omitted. Also asserts a non-skipped sibling task still runs to ensure the pipeline wasn’t short-circuited.

e2e/harmony/ci-commands.e2e.ts

Documentation (3) +16 / -10

CLI_REFERENCE.mdDocument '--skip-tasks' in 'bit ci pr' flags list +1/-1

Document '--skip-tasks' in 'bit ci pr' flags list
• Extends the 'bit ci pr' documentation to include the new '--skip-tasks <tasks>' option.
contrib/claude-skill-bit-cli/CLI_REFERENCE.md

cli-reference.jsonUpdate generated CLI reference JSON for '--skip-tasks' +5/-0

Update generated CLI reference JSON for '--skip-tasks'
• Adds the 'skip-tasks <tasks>' option entry and description to the machine-readable CLI reference for 'bit ci pr'.
scopes/harmony/cli-reference/cli-reference.json

cli-reference.mdxUpdate CLI reference MDX with '--skip-tasks' option +10/-9

Update CLI reference MDX with '--skip-tasks' option
• Extends the 'bit ci pr' options table to include '--skip-tasks <tasks>' with guidance and an example list.
scopes/harmony/cli-reference/cli-reference.mdx

Other (1) +3 / -1

config.ymlSpeed up 'bit ci pr' by skipping schema/preview and publish tasks +3/-1

Speed up 'bit ci pr' by skipping schema/preview and publish tasks

• Updates the 'bit_pr' CircleCI job to pass '--skip-tasks' for ExtractSchema, GeneratePreview, GenerateEnvTemplate, and PublishComponents. Documents why the tasks are safe to skip on throwaway PR lanes and calls out the expected time savings.

.circleci/config.yml

qodo-free-for-open-source-projects · 2026-06-22T13:33:31Z

Code Review by Qodo

🐞 Bugs (4) 📘 Rule violations (1) 📜 Skill insights (0)

1. Skipping tasks uses chalk 📘 Rule violation ⚙ Maintainability ⭐ New

Description

The PR adds a new CLI output line styled with hardcoded chalk.blue(...), bypassing the shared CLI
output formatting utilities. This can lead to inconsistent CLI output and violates the requirement
to use the shared output formatter/style guide for CLI output changes.

Code

scopes/git/ci/ci.main.runtime.ts[R584-586]

+    if (messageSkipTasks.length) {
+      this.logger.console(chalk.blue(`Skipping tasks from commit message: ${messageSkipTasks.join(', ')}`));
+    }

Evidence
PR Compliance ID 1 prohibits introducing hardcoded chalk styling for CLI output and requires using
the shared CLI output formatter. The added line prints Skipping tasks from commit message: ...
using chalk.blue(...), which is inline styling rather than the shared formatter.
CLAUDE.md: CLI Output Must Follow Style Guide and Use Shared Output Formatter (No Hardcoded Chalk/Unicode for Titles)
scopes/git/ci/ci.main.runtime.ts[584-586]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
A new CLI output line was added using hardcoded `chalk.blue(...)` (`Skipping tasks from commit message: ...`). The style guide requires using the shared `@teambit/cli` output formatting utilities instead of inline chalk styling.

## Issue Context
This output is part of `bit ci pr` execution and is user-facing.

## Fix Focus Areas
- scopes/git/ci/ci.main.runtime.ts[584-586]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

2. Token ignored with --message 🐞 Bug ≡ Correctness ⭐ New

Description

The new [skip-tasks: ...] commit-message token is not parsed when bit ci pr is invoked with
--message, because the command stops reading the git commit message and the token extraction runs
only against the selected snap message string. This makes the documented “commit-message token”
behavior inconsistent in a common usage path.

Code

scopes/git/ci/ci.main.runtime.ts[R570-576]

+    // Skipping build/publish tasks is OPT-IN per PR: the build runs the full pipeline by default, and
+    // a developer adds a `[skip-tasks: <names>]` token to the commit message to trade specific tasks
+    // for speed on that PR (e.g. `[skip-tasks: GeneratePreview,ExtractSchema]`) without touching CI
+    // config. The token merges with any explicit `--skip-tasks` flag, and is stripped from the message
+    // so it doesn't leak into the snap message.
+    const { skipTasks: messageSkipTasks, message: resolvedMessage } = extractSkipTasksFromMessage(message);
+    const cliSkipTasks = skipTasks

Evidence

CiPrCmd chooses between --message and the git commit message; the new token parsing in CiMain
runs only on that chosen message value, so tokens in the git commit message are bypassed whenever
--message is set.

scopes/git/ci/commands/pr.cmd.ts[72-80]
scopes/git/ci/ci.main.runtime.ts[570-576]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
When `--message` is provided, `bit ci pr` uses that string as `message` and does not read the git commit message. The new skip-tasks token parsing runs against `message`, so a token placed in the *git commit message* will be ignored in this path.

### Issue Context
- Docs/comments describe the feature as a **commit-message token**.
- Current flow: `CiPrCmd` sets `message = options.message` when provided, otherwise reads git commit message; then `CiMain.snapPrCommit()` calls `extractSkipTasksFromMessage(message)`.

### Fix Focus Areas
- scopes/git/ci/commands/pr.cmd.ts[72-91]
- scopes/git/ci/ci.main.runtime.ts[570-584]

### Suggested fix options (pick one)
1) **Behavioral fix (preferred):** Always read the git commit message (when available) specifically for parsing `[skip-tasks: ...]`, even if `--message` is supplied for the snap message. Then:
  - Parse skip-tasks from git commit message.
  - Strip the token from the snap message only when the snap message is sourced from git commit message (or explicitly document stripping from `--message` if you keep that behavior).
2) **Documentation fix:** If intended behavior is “token may be included in the effective message string (including `--message`)”, update help/docs/comments to remove the claim that it is a commit-message token.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

3. skip-tasks needs --build 🐞 Bug ≡ Correctness

Description

bit ci pr --skip-tasks becomes a no-op when --build isn’t enabled, because task-skipping is only
applied inside VersionMaker.build() after an early return when params.build is falsy. This makes
the new flag misleading for the default “build on Ripple CI” path.

Code

scopes/git/ci/commands/pr.cmd.ts[R39-43]

+    [
+      '',
+      'skip-tasks <tasks>',
+      `Comma-separated list of build/publish task names (or aspect-ids) to skip during snap, e.g. "ExtractSchema,GeneratePreview,GenerateEnvTemplate,PublishComponents". Speeds up PR builds by trading optional artifacts (schema/preview) and publishing for build time; they are produced on the final export to main`,
+    ],

Evidence

ci pr documents that non---build runs build on Ripple CI, but the only place skipTasks is
parsed/applied is inside VersionMaker.build(), which returns immediately when params.build is
falsy; therefore no task filtering happens without --build.

scopes/git/ci/commands/pr.cmd.ts[23-44]
scopes/component/snapping/version-maker.ts[330-358]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`bit ci pr` now exposes `--skip-tasks`, but pipeline task skipping is only applied when running the local build pipeline (`--build`). When `--build` is omitted (default is Ripple CI), the flag won’t actually skip tasks, which is misleading and can surprise users.
### Issue Context
- `ci pr` help text says `--build` is required for local pipeline execution; otherwise builds happen on Ripple CI.
- The actual skip logic is only applied in the local build path (`VersionMaker.build()`), which early-returns when `build` is falsy.
### Fix Focus Areas
- scopes/git/ci/commands/pr.cmd.ts[23-43]
- scopes/component/snapping/version-maker.ts[330-358]
### Suggested fix directions
Choose one (or combine):
1. **Behavior guard**: if `--skip-tasks` is provided without `--build` (and without a forced-local-build config), fail fast with a clear error (or at least log a prominent warning that it won’t have any effect).
2. **Documentation fix**: update the `--skip-tasks` option description in `ci pr` (and the generated cli-reference docs) to explicitly say it only applies when running locally (`--build`).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

View more (1)

4. Unvalidated skip-tasks names 🐞 Bug ☼ Reliability

Description

bit ci pr --skip-tasks accepts any comma-separated string, but the builder pipeline only filters
tasks by string match and does not validate that the requested task names/aspect-ids exist. If a
task name is misspelled or renamed, it will silently run anyway (including PublishComponents,
which performs npm publish).

Code

scopes/git/ci/commands/pr.cmd.ts[R39-43]

+    [
+      '',
+      'skip-tasks <tasks>',
+      `Comma-separated list of build/publish task names (or aspect-ids) to skip during snap, e.g. "ExtractSchema,GeneratePreview,GenerateEnvTemplate,PublishComponents". Speeds up PR builds by trading optional artifacts (schema/preview) and publishing for build time; they are produced on the final export to main`,
+    ],

Evidence
CI now depends on --skip-tasks ... PublishComponents to avoid publishing, but the pipeline skip
implementation only filters and never errors on unknown skip entries, so a typo/rename would still
execute the publish task. The publish task explicitly runs npm publish, making the fail-open
behavior meaningful.
.circleci/config.yml[754-762]
scopes/pipelines/builder/build-pipeline-order.ts[75-95]
scopes/pkg/pkg/publish.task.ts[6-36]
scopes/git/ci/commands/pr.cmd.ts[23-44]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`--skip-tasks` currently fails open: unknown task names are silently ignored, so the tasks still execute. This is risky for CI usage (e.g. skipping `PublishComponents` to avoid `npm publish`) because a typo or a future rename will re-enable the task without any explicit failure.
### Issue Context
- `bit ci pr` exposes `--skip-tasks` and CI now relies on it to skip publish/schema/preview tasks.
- The builder pipeline applies `skipTasks` via filtering but does not check that each requested skip name/aspect-id is present in the pipeline.
### Fix Focus Areas
- scopes/pipelines/builder/build-pipeline-order.ts[46-97]
### Proposed fix
- In `calculatePipelineOrder(...)`, compute `available = new Set([...flattenedPipeline task.name and task.aspectId])`.
- If `skipTasks.length > 0`, compute `unknown = skipTasks.filter(t => !available.has(t))`.
- If `unknown.length > 0`, throw an Error (preferred for CI safety) listing the unknown entries and the available tasks (reuse `getAvailableTaskNames(flattenedPipeline)`), or at minimum `console.warn`/logger warning + continue.
- Add/adjust an e2e/unit test to assert unknown skip tasks fail fast (or warn) to prevent silent regressions.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

5. Multiple tokens not stripped 🐞 Bug ⚙ Maintainability ⭐ New

Description

extractSkipTasksFromMessage() removes only the first [skip-tasks: ...] token, so if a commit
message contains multiple tokens, subsequent tokens remain in the snap message despite the intent to
prevent token leakage. Example: "msg [skip-tasks: A] more [skip-tasks: B]" becomes `"msg more
[skip-tasks: B]"`.

Code

scopes/git/ci/skip-tasks-from-message.ts[R9-21]

+const SKIP_TASKS_TOKEN = /\[skip-tasks:\s*([^\]]+?)\s*\]/i;
+
+export function extractSkipTasksFromMessage(message: string): { skipTasks: string[]; message: string } {
+  const match = message.match(SKIP_TASKS_TOKEN);
+  if (!match) return { skipTasks: [], message };
+  const skipTasks = match[1]
+    .split(',')
+    .map((task) => task.trim())
+    .filter(Boolean);
+  const cleanedMessage = message
+    .replace(match[0], '')
+    .replace(/[ \t]{2,}/g, ' ')
+    .trim();

Evidence

The token is intended to be stripped from the message to avoid leaking into the snap message, but
the implementation matches and replaces only a single occurrence (the first match), leaving any
additional tokens untouched.

scopes/git/ci/skip-tasks-from-message.ts[1-22]
scopes/git/ci/ci.main.runtime.ts[570-576]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

### Issue description
`extractSkipTasksFromMessage()` parses the first `[skip-tasks: ...]` token but only strips that one occurrence from the message. If multiple tokens exist, later ones leak into the resolved snap message.

### Issue Context
- The function explicitly says only the first token is honored, but the message-cleaning intent is “token doesn't leak into the snap message”.
- Current implementation uses a non-global regex and `.replace(match[0], '')`, which removes only the first match.

### Fix Focus Areas
- scopes/git/ci/skip-tasks-from-message.ts[1-23]
- scopes/git/ci/skip-tasks-from-message.spec.ts[1-32]

### Suggested fix
- Keep parsing only the first token for `skipTasks` (as documented), but strip *all* `[skip-tasks: ...]` tokens from the returned `message` (e.g. use a global regex for removal, or loop replacements).
- Add a unit test covering multiple tokens to ensure the returned message contains none of them.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Previous review results

Review updated until commit f68d99c

Results up to commit N/A

🐞 Bugs (2) 📘 Rule violations (0) 📎 Requirement gaps (0) 🎨 UX issues (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

1. skip-tasks needs --build 🐞 Bug ≡ Correctness

Description

bit ci pr --skip-tasks becomes a no-op when --build isn’t enabled, because task-skipping is only
applied inside VersionMaker.build() after an early return when params.build is falsy. This makes
the new flag misleading for the default “build on Ripple CI” path.

Code

scopes/git/ci/commands/pr.cmd.ts[R39-43]

+    [
+      '',
+      'skip-tasks <tasks>',
+      `Comma-separated list of build/publish task names (or aspect-ids) to skip during snap, e.g. "ExtractSchema,GeneratePreview,GenerateEnvTemplate,PublishComponents". Speeds up PR builds by trading optional artifacts (schema/preview) and publishing for build time; they are produced on the final export to main`,
+    ],

Evidence

ci pr documents that non---build runs build on Ripple CI, but the only place skipTasks is
parsed/applied is inside VersionMaker.build(), which returns immediately when params.build is
falsy; therefore no task filtering happens without --build.

scopes/git/ci/commands/pr.cmd.ts[23-44]
scopes/component/snapping/version-maker.ts[330-358]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`bit ci pr` now exposes `--skip-tasks`, but pipeline task skipping is only applied when running the local build pipeline (`--build`). When `--build` is omitted (default is Ripple CI), the flag won’t actually skip tasks, which is misleading and can surprise users.
### Issue Context
- `ci pr` help text says `--build` is required for local pipeline execution; otherwise builds happen on Ripple CI.
- The actual skip logic is only applied in the local build path (`VersionMaker.build()`), which early-returns when `build` is falsy.
### Fix Focus Areas
- scopes/git/ci/commands/pr.cmd.ts[23-43]
- scopes/component/snapping/version-maker.ts[330-358]
### Suggested fix directions
Choose one (or combine):
1. **Behavior guard**: if `--skip-tasks` is provided without `--build` (and without a forced-local-build config), fail fast with a clear error (or at least log a prominent warning that it won’t have any effect).
2. **Documentation fix**: update the `--skip-tasks` option description in `ci pr` (and the generated cli-reference docs) to explicitly say it only applies when running locally (`--build`).

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

2. Unvalidated skip-tasks names 🐞 Bug ☼ Reliability

Description

bit ci pr --skip-tasks accepts any comma-separated string, but the builder pipeline only filters
tasks by string match and does not validate that the requested task names/aspect-ids exist. If a
task name is misspelled or renamed, it will silently run anyway (including PublishComponents,
which performs npm publish).

Code

scopes/git/ci/commands/pr.cmd.ts[R39-43]

+    [
+      '',
+      'skip-tasks <tasks>',
+      `Comma-separated list of build/publish task names (or aspect-ids) to skip during snap, e.g. "ExtractSchema,GeneratePreview,GenerateEnvTemplate,PublishComponents". Speeds up PR builds by trading optional artifacts (schema/preview) and publishing for build time; they are produced on the final export to main`,
+    ],

Evidence
CI now depends on --skip-tasks ... PublishComponents to avoid publishing, but the pipeline skip
implementation only filters and never errors on unknown skip entries, so a typo/rename would still
execute the publish task. The publish task explicitly runs npm publish, making the fail-open
behavior meaningful.
.circleci/config.yml[754-762]
scopes/pipelines/builder/build-pipeline-order.ts[75-95]
scopes/pkg/pkg/publish.task.ts[6-36]
scopes/git/ci/commands/pr.cmd.ts[23-44]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`--skip-tasks` currently fails open: unknown task names are silently ignored, so the tasks still execute. This is risky for CI usage (e.g. skipping `PublishComponents` to avoid `npm publish`) because a typo or a future rename will re-enable the task without any explicit failure.
### Issue Context
- `bit ci pr` exposes `--skip-tasks` and CI now relies on it to skip publish/schema/preview tasks.
- The builder pipeline applies `skipTasks` via filtering but does not check that each requested skip name/aspect-id is present in the pipeline.
### Fix Focus Areas
- scopes/pipelines/builder/build-pipeline-order.ts[46-97]
### Proposed fix
- In `calculatePipelineOrder(...)`, compute `available = new Set([...flattenedPipeline task.name and task.aspectId])`.
- If `skipTasks.length > 0`, compute `unknown = skipTasks.filter(t => !available.has(t))`.
- If `unknown.length > 0`, throw an Error (preferred for CI safety) listing the unknown entries and the available tasks (reuse `getAvailableTaskNames(flattenedPipeline)`), or at minimum `console.warn`/logger warning + continue.
- Add/adjust an e2e/unit test to assert unknown skip tasks fail fast (or warn) to prevent silent regressions.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

The schema/preview artifacts and npm publish are generally useful (browsable preview, API schema, installable packages); we're deliberately skipping them on the PR validation lane to optimize for speed, not because they're never needed. They're still produced on the final export to main.

qodo-free-for-open-source-projects · 2026-06-22T13:38:01Z

Code review by qodo was updated up to the latest commit 9e9b50b

qodo-free-for-open-source-projects · 2026-06-23T19:45:46Z

Code review by qodo was updated up to the latest commit 4511d7d

qodo-free-for-open-source-projects · 2026-06-24T13:47:21Z

Code review by qodo was updated up to the latest commit 08ae96c

qodo-free-for-open-source-projects · 2026-06-24T19:57:13Z

Code review by qodo was updated up to the latest commit abff5ab

qodo-free-for-open-source-projects · 2026-06-25T14:53:04Z

Code review by qodo was updated up to the latest commit f86dad6

Invert the default: bit ci pr now runs the full pipeline by default. A developer opts into skipping specific tasks for a single PR by adding a [skip-tasks: <names>] token to the commit message (e.g. [skip-tasks: GeneratePreview,ExtractSchema]) — no CircleCI YAML change needed. The token is parsed in snapPrCommit, merges with any --skip-tasks flag, and is stripped from the snap message. Removes the hardcoded --skip-tasks list from the bit_pr job. Adds a pure parser (extractSkipTasksFromMessage) with unit specs, plus an e2e for the token path.

qodo-free-for-open-source-projects · 2026-06-26T14:55:45Z

Code review by qodo was updated up to the latest commit f68d99c

Merge branch 'master' into optimize-ci-pr-skip-tasks

4511d7d

Merge branch 'master' into optimize-ci-pr-skip-tasks

08ae96c

Merge branch 'master' into optimize-ci-pr-skip-tasks

abff5ab

Merge branch 'master' into optimize-ci-pr-skip-tasks

f86dad6

davidfirst mentioned this pull request Jun 25, 2026

[DO NOT MERGE] test: control for registry experiment (no registry change) #10455

Closed

davidfirst changed the title ~~feat(ci): add --skip-tasks flag to bit ci pr~~ feat(ci): add --skip-tasks flag + opt-in [skip-tasks] commit token to bit ci pr Jun 26, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

feat(ci): add --skip-tasks flag + opt-in [skip-tasks] commit token to bit ci pr#10436

feat(ci): add --skip-tasks flag + opt-in [skip-tasks] commit token to bit ci pr#10436
davidfirst wants to merge 7 commits into
masterfrom
optimize-ci-pr-skip-tasks

davidfirst commented Jun 22, 2026 •

edited

Loading

Uh oh!

qodo-free-for-open-source-projects Bot commented Jun 22, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Jun 22, 2026 •

edited

Loading

Uh oh!

qodo-free-for-open-source-projects Bot commented Jun 22, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Jun 23, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Jun 24, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Jun 24, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Jun 25, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Jun 26, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

davidfirst commented Jun 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

qodo-free-for-open-source-projects Bot commented Jun 22, 2026

PR Summary by Qodo

Uh oh!

qodo-free-for-open-source-projects Bot commented Jun 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Code Review by Qodo

Previous review results

Uh oh!

qodo-free-for-open-source-projects Bot commented Jun 22, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Jun 23, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Jun 24, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Jun 24, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Jun 25, 2026

Uh oh!

qodo-free-for-open-source-projects Bot commented Jun 26, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

davidfirst commented Jun 22, 2026 •

edited

Loading

qodo-free-for-open-source-projects Bot commented Jun 22, 2026 •

edited

Loading