Overview - Nx

Nx

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Canceled
master
68d4d4e9 fix(js): check package.json for name when project.json exists but has no name (#31887) ## Current Behavior When a project has a `project.json` file but no `name` field, the `addBuildAndWatchDepsTargets` function in `packages/js/src/plugins/typescript/util.ts` returns early without creating build and watch deps targets, even if the project has a valid name in its `package.json`. ## Expected Behavior The function should fall back to checking `package.json` for the project name when `project.json` exists but has no `name` field, allowing the build and watch deps targets to be created properly. ## Related Issue(s) This fixes an issue where projects with `project.json` files missing the `name` field would not get proper build and watch dependency targets generated. 🤖 Generated with [Claude Code](https://claude.ai/code) --------- Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: Colum Ferry <cferry09@gmail.com>
7 days ago by ZackDeRose
Failed
31887
Fix ready→
254ee272 fix(js): check package.json for name when project.json exists but has no name When a project.json exists but has no name field, now falls back to checking package.json for project name in build and watch deps targets. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
7 days ago by ZackDeRose
Failed
33660
16821753 chore(core): apply cargo fmt to hash_project_files
25 days ago by ZackDeRose
Canceled
33660
Generating fix→
f7579c82 fix(core): hash git-ignored files when explicitly listed as inputs Git-ignored files that are explicitly specified as task inputs were not being hashed, causing incorrect cache hits when these files changed. This fix walks the filesystem to find git-ignored files that match input patterns and includes them in the hash computation. Changes: - Modified hash_project_files to check for missing git-ignored files - Modified hash_workspace_files to check for missing git-ignored files - Added Rust unit test to verify git-ignored files are hashed - Added e2e test demonstrating the fix Note: This implementation hashes ALL git-ignored files matching input patterns, including broad wildcards like **/*. The team should review whether this should be limited to only explicit file specifications. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
25 days ago by ZackDeRose
Succeeded
master
4fcd1d22 fix(core): adding output error reason (#33159)      ## Current Behavior  When an invalid output exists we report: ``` NX The following outputs are invalid: - foo.txt Run `nx repair` to fix this. ``` Without specifying the reason, we tell to run `nx repair`. ## Expected Behavior  More feedback provided to the user as to the error with their output: ``` NX The following outputs are invalid: - foo.txt ** Reason: Outputs must start with either "{workspaceRoot}/" or "{projectRoot}/". Run `nx repair` to fix this. ``` ## Related Issue(s)  Fixes #
2 months ago by ZackDeRose
Succeeded
master
4fcd1d22 fix(core): adding output error reason (#33159)      ## Current Behavior  When an invalid output exists we report: ``` NX The following outputs are invalid: - foo.txt Run `nx repair` to fix this. ``` Without specifying the reason, we tell to run `nx repair`. ## Expected Behavior  More feedback provided to the user as to the error with their output: ``` NX The following outputs are invalid: - foo.txt ** Reason: Outputs must start with either "{workspaceRoot}/" or "{projectRoot}/". Run `nx repair` to fix this. ``` ## Related Issue(s)  Fixes #
2 months ago by ZackDeRose
Succeeded
master
4fcd1d22 fix(core): adding output error reason (#33159)      ## Current Behavior  When an invalid output exists we report: ``` NX The following outputs are invalid: - foo.txt Run `nx repair` to fix this. ``` Without specifying the reason, we tell to run `nx repair`. ## Expected Behavior  More feedback provided to the user as to the error with their output: ``` NX The following outputs are invalid: - foo.txt ** Reason: Outputs must start with either "{workspaceRoot}/" or "{projectRoot}/". Run `nx repair` to fix this. ``` ## Related Issue(s)  Fixes #
2 months ago by ZackDeRose
Succeeded
master
4fcd1d22 fix(core): adding output error reason (#33159)      ## Current Behavior  When an invalid output exists we report: ``` NX The following outputs are invalid: - foo.txt Run `nx repair` to fix this. ``` Without specifying the reason, we tell to run `nx repair`. ## Expected Behavior  More feedback provided to the user as to the error with their output: ``` NX The following outputs are invalid: - foo.txt ** Reason: Outputs must start with either "{workspaceRoot}/" or "{projectRoot}/". Run `nx repair` to fix this. ``` ## Related Issue(s)  Fixes #
2 months ago by ZackDeRose
Succeeded
master
4fcd1d22 fix(core): adding output error reason (#33159)      ## Current Behavior  When an invalid output exists we report: ``` NX The following outputs are invalid: - foo.txt Run `nx repair` to fix this. ``` Without specifying the reason, we tell to run `nx repair`. ## Expected Behavior  More feedback provided to the user as to the error with their output: ``` NX The following outputs are invalid: - foo.txt ** Reason: Outputs must start with either "{workspaceRoot}/" or "{projectRoot}/". Run `nx repair` to fix this. ``` ## Related Issue(s)  Fixes #
2 months ago by ZackDeRose
Succeeded
33159
96f503e0 Merge branch 'master' into adding-output-error-reason
2 months ago by ZackDeRose