Overview

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
35863
d3676648 feat(core): suggest available targets and closest task id on run-one errors [Self-Healing CI Rerun]
by nx-cloud[bot]
Failed
35863
7b6cfc3b feat(core): suggest available targets and closest task id on run-one errors [Self-Healing CI Rerun]
by nx-cloud[bot]
Failed
35863
Flaky task→
9b073fff feat(core): suggest available targets and closest task id on run-one errors - When `nx run <project>:<target>` references an unknown target, list up to 5 available targets and surface the closest match as 'Did you mean ...?'. - When the project itself is unknown, match the attempted `project:target[:configuration]` against every `project:target` task id in the graph so project typos (e.g. `webpai:build`) suggest the real invocation (`webapi:build`). - Handle colon-containing target/configuration names: when `splitTarget` parses the trailing segment off into a configuration, the rejoined specifier is tried first, then progressively shorter forms - so `nx:zzcustom:variantt` still suggests `zzcustom:variant`, while genuine `target` + `configuration` typos (`biuld:production` -> `build`) keep working via the shorter-form fallback. - New `findClosestMatches` / `findClosestMatch` Levenshtein helper with a length-relative threshold (no suggestion for total nonsense). - Update e2e assertion for the friendlier message. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
by Craigory C...
Failed
35863
Flaky task→
9b073fff feat(core): suggest available targets and closest task id on run-one errors - When `nx run <project>:<target>` references an unknown target, list up to 5 available targets and surface the closest match as 'Did you mean ...?'. - When the project itself is unknown, match the attempted `project:target[:configuration]` against every `project:target` task id in the graph so project typos (e.g. `webpai:build`) suggest the real invocation (`webapi:build`). - Handle colon-containing target/configuration names: when `splitTarget` parses the trailing segment off into a configuration, the rejoined specifier is tried first, then progressively shorter forms - so `nx:zzcustom:variantt` still suggests `zzcustom:variant`, while genuine `target` + `configuration` typos (`biuld:production` -> `build`) keep working via the shorter-form fallback. - New `findClosestMatches` / `findClosestMatch` Levenshtein helper with a length-relative threshold (no suggestion for total nonsense). - Update e2e assertion for the friendlier message. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
by Craigory C...