JavaScriptExpert
diff --git a/‎apps/rush-lib/src/cli/RushCommandLineParser.ts‎
Lines changed: 3 additions & 3 deletions b/‎apps/rush-lib/src/cli/RushCommandLineParser.ts‎
Lines changed: 3 additions & 3 deletions
diff --git a/‎apps/rush-lib/src/cli/test/RushCommandLineParser.test.ts‎
Lines changed: 2 additions & 2 deletions b/‎apps/rush-lib/src/cli/test/RushCommandLineParser.test.ts‎
Lines changed: 2 additions & 2 deletions
diff --git a/‎apps/rush-lib/src/cli/test/__snapshots__/CommandLineHelp.test.ts.snap‎
Lines changed: 5 additions & 4 deletions b/‎apps/rush-lib/src/cli/test/__snapshots__/CommandLineHelp.test.ts.snap‎
Lines changed: 5 additions & 4 deletions
@@ -206,9 +206,9 @@ export class RushCommandLineParser extends CommandLineParser {
           + ' since the last successful build. The analysis requires a Git working tree, and only considers'
           + ' source files that are tracked by Git and whose path is under the project folder. (For more details'
           + ' about this algorithm, see the documentation for the "package-deps-hash" NPM package.) The incremental'
-          + ' build state is tracked in a folder called ".rush" which should NOT be added to Git. The build command is'
-          + ' tracked by the "arguments" field in the "package-deps_build.json" file contained therein; a full'
-          + ' rebuild is forced whenever the command has changed (e.g. "--production" or not).',
+          + ' build state is tracked in a per-project folder called ".rush/temp" which should NOT be added to Git. The'
+          + ' build command is tracked by the "arguments" field in the "package-deps_build.json" file contained'
+          + ' therein; a full rebuild is forced whenever the command has changed (e.g. "--production" or not).',
         parser: this,
         commandLineConfiguration: commandLineConfiguration,
 
 
@@ -45,8 +45,8 @@ function getCommandLineParserInstance(repoName: string, taskName: string): IPars
 
   // The `build` task is hard-coded to be incremental. So delete the package-deps file folder in
   // the test repo to guarantee the test actually runs.
-  FileSystem.deleteFolder(resolve(__dirname, `${repoName}/a/.rush`));
-  FileSystem.deleteFolder(resolve(__dirname, `${repoName}/b/.rush`));
+  FileSystem.deleteFolder(resolve(__dirname, `${repoName}/a/.rush/temp`));
+  FileSystem.deleteFolder(resolve(__dirname, `${repoName}/b/.rush/temp`));
 
   // Create a Rush CLI instance. This instance is heavy-weight and relies on setting process.exit
   // to exit and clear the Rush file lock. So running multiple `it` or `describe` test blocks over the same test
 
@@ -105,10 +105,11 @@ files have changed since the last successful build. The analysis requires a
 Git working tree, and only considers source files that are tracked by Git and 
 whose path is under the project folder. (For more details about this 
 algorithm, see the documentation for the \\"package-deps-hash\\" NPM package.) 
-The incremental build state is tracked in a folder called \\".rush\\" which 
-should NOT be added to Git. The build command is tracked by the \\"arguments\\" 
-field in the \\"package-deps_build.json\\" file contained therein; a full rebuild 
-is forced whenever the command has changed (e.g. \\"--production\\" or not).
+The incremental build state is tracked in a per-project folder called \\".
+rush/temp\\" which should NOT be added to Git. The build command is tracked by 
+the \\"arguments\\" field in the \\"package-deps_build.json\\" file contained 
+therein; a full rebuild is forced whenever the command has changed (e.g. 
+\\"--production\\" or not).
 
 Optional arguments:
   -h, --help            Show this help message and exit.