fix: isolate tests from CI environment variables

Tests were failing on GitHub Actions because GITHUB_ACTIONS env var
triggers CI metadata appending to commit messages. Tests now explicitly
clear CI environment variables to ensure consistent behavior.

Author: JohannesHoppe

src/parameter-tests/builder-integration.spec.ts

@@ -88,19 +88,31 @@ import * as engine from '../engine/engine';
 
 describe('Angular Builder Integration Tests', () => {
   let context: BuilderContext;
+  let originalEnv: NodeJS.ProcessEnv;
 
   const PROJECT = 'test-project';
   const BUILD_TARGET: BuildTarget = {
     name: `${PROJECT}:build:production`
   };
 
   beforeEach(() => {
+    // Save and clear CI environment variables to ensure consistent test behavior
+    originalEnv = { ...process.env };
+    delete process.env.TRAVIS;
+    delete process.env.CIRCLECI;
+    delete process.env.GITHUB_ACTIONS;
+
     // Clean up any previous monkeypatch so each test starts fresh
     cleanupMonkeypatch();
     capturedPublishOptions = null;
     context = createMockContext();
   });
 
+  afterEach(() => {
+    // Restore original environment
+    process.env = originalEnv;
+  });
+
   afterAll(() => {
     // Clean up monkeypatch after all tests
     cleanupMonkeypatch();

src/parameter-tests/cli-e2e.spec.ts

@@ -34,7 +34,13 @@ function runCli(args: string): string {
   }
 
   const program = path.resolve(__dirname, '../dist/angular-cli-ghpages');
-  return execSync(`node ${program} --dry-run ${args}`).toString();
+  // Clear CI environment variables to ensure consistent test behavior across environments
+  const env = { ...process.env };
+  delete env.TRAVIS;
+  delete env.CIRCLECI;
+  delete env.GITHUB_ACTIONS;
+
+  return execSync(`node ${program} --dry-run ${args}`, { env }).toString();
 }
 
 function parseJsonFromCliOutput(output: string): DryRunOutput {