Fix CI failure: mock setFailed to prevent process.exitCode=1 in tests

[Copilot]

core.setFailed() from @actions/core sets process.exitCode = 1 as a side effect. Negative test scenarios trigger this, causing jest to exit with code 1 even when all 33 tests pass — failing the CI test step.

Changes

• __test__/main.test.ts: Add a partial mock for @actions/core that replaces setFailed with a no-op jest.fn() while preserving real implementations of getInput, info, setOutput, etc. via jest.requireActual.

jest.mock("@actions/core",()=>({
...jest.requireActual("@actions/core"),setFailed: jest.fn(),}));

This prevents process.exitCode from being set during the test run, so jest exits cleanly with code 0 on a passing suite.

Original prompt

Fix the failing GitHub Actions workflow ci
Analyze the workflow logs, identify the root cause of the failure, and implement a fix.
Job ID: 67293922127
Job URL: https://github.com/github/update-project-action/actions/runs/23162076204/job/67293922127

---

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.

[Copilot]

Pull request overview

Adjusts the Jest test environment to avoid @actions/core.setFailed()’s side effect (process.exitCode = 1) causing CI failures when negative-path tests run.

Changes:

• Add a partial Jest mock for @actions/core that preserves real exports but replaces setFailed with a no-op jest.fn().

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

[Copilot]

core.setFailed() from @actions/core sets process.exitCode = 1 as a side effect. Negative test scenarios trigger this, causing jest to exit with code 1 even when all 33 tests pass — failing the CI test step.

Changes

• __test__/main.test.ts: Add a partial mock for @actions/core that replaces setFailed with a no-op jest.fn() while preserving real implementations of getInput, info, setOutput, etc. via jest.requireActual.

jest.mock("@actions/core",()=>({
...jest.requireActual("@actions/core"),setFailed: jest.fn(),}));

This prevents process.exitCode from being set during the test run, so jest exits cleanly with code 0 on a passing suite.

Original prompt

Fix the failing GitHub Actions workflow ci
Analyze the workflow logs, identify the root cause of the failure, and implement a fix.
Job ID: 67293922127
Job URL: https://github.com/github/update-project-action/actions/runs/23162076204/job/67293922127

---

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.

[Copilot]

Pull request overview

Adjusts the Jest test environment to avoid @actions/core.setFailed()’s side effect (process.exitCode = 1) causing CI failures when negative-path tests run.

Changes:

• Add a partial Jest mock for @actions/core that preserves real exports but replaces setFailed with a no-op jest.fn().

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

[Copilot]

core.setFailed() from @actions/core sets process.exitCode = 1 as a side effect. Negative test scenarios trigger this, causing jest to exit with code 1 even when all 33 tests pass — failing the CI test step.

Changes

• __test__/main.test.ts: Add a partial mock for @actions/core that replaces setFailed with a no-op jest.fn() while preserving real implementations of getInput, info, setOutput, etc. via jest.requireActual.

jest.mock("@actions/core",()=>({
...jest.requireActual("@actions/core"),setFailed: jest.fn(),}));

This prevents process.exitCode from being set during the test run, so jest exits cleanly with code 0 on a passing suite.

Original prompt

Fix the failing GitHub Actions workflow ci
Analyze the workflow logs, identify the root cause of the failure, and implement a fix.
Job ID: 67293922127
Job URL: https://github.com/github/update-project-action/actions/runs/23162076204/job/67293922127

---

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.

[Copilot]

Pull request overview

Adjusts the Jest test environment to avoid @actions/core.setFailed()’s side effect (process.exitCode = 1) causing CI failures when negative-path tests run.

Changes:

• Add a partial Jest mock for @actions/core that preserves real exports but replaces setFailed with a no-op jest.fn().

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

[Copilot]

core.setFailed() from @actions/core sets process.exitCode = 1 as a side effect. Negative test scenarios trigger this, causing jest to exit with code 1 even when all 33 tests pass — failing the CI test step.

Changes

• __test__/main.test.ts: Add a partial mock for @actions/core that replaces setFailed with a no-op jest.fn() while preserving real implementations of getInput, info, setOutput, etc. via jest.requireActual.

jest.mock("@actions/core",()=>({
...jest.requireActual("@actions/core"),setFailed: jest.fn(),}));

This prevents process.exitCode from being set during the test run, so jest exits cleanly with code 0 on a passing suite.

Original prompt

Fix the failing GitHub Actions workflow ci
Analyze the workflow logs, identify the root cause of the failure, and implement a fix.
Job ID: 67293922127
Job URL: https://github.com/github/update-project-action/actions/runs/23162076204/job/67293922127

---

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.

[Copilot]

Pull request overview

Adjusts the Jest test environment to avoid @actions/core.setFailed()’s side effect (process.exitCode = 1) causing CI failures when negative-path tests run.

Changes:

• Add a partial Jest mock for @actions/core that preserves real exports but replaces setFailed with a no-op jest.fn().

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

[Copilot]

core.setFailed() from @actions/core sets process.exitCode = 1 as a side effect. Negative test scenarios trigger this, causing jest to exit with code 1 even when all 33 tests pass — failing the CI test step.

Changes

• __test__/main.test.ts: Add a partial mock for @actions/core that replaces setFailed with a no-op jest.fn() while preserving real implementations of getInput, info, setOutput, etc. via jest.requireActual.

jest.mock("@actions/core",()=>({
...jest.requireActual("@actions/core"),setFailed: jest.fn(),}));

This prevents process.exitCode from being set during the test run, so jest exits cleanly with code 0 on a passing suite.

Original prompt

Fix the failing GitHub Actions workflow ci
Analyze the workflow logs, identify the root cause of the failure, and implement a fix.
Job ID: 67293922127
Job URL: https://github.com/github/update-project-action/actions/runs/23162076204/job/67293922127

---

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.

[Copilot]

Pull request overview

Adjusts the Jest test environment to avoid @actions/core.setFailed()’s side effect (process.exitCode = 1) causing CI failures when negative-path tests run.

Changes:

• Add a partial Jest mock for @actions/core that preserves real exports but replaces setFailed with a no-op jest.fn().

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

[Copilot]

core.setFailed() from @actions/core sets process.exitCode = 1 as a side effect. Negative test scenarios trigger this, causing jest to exit with code 1 even when all 33 tests pass — failing the CI test step.

Changes

• __test__/main.test.ts: Add a partial mock for @actions/core that replaces setFailed with a no-op jest.fn() while preserving real implementations of getInput, info, setOutput, etc. via jest.requireActual.

jest.mock("@actions/core",()=>({
...jest.requireActual("@actions/core"),setFailed: jest.fn(),}));

This prevents process.exitCode from being set during the test run, so jest exits cleanly with code 0 on a passing suite.

Original prompt

Fix the failing GitHub Actions workflow ci
Analyze the workflow logs, identify the root cause of the failure, and implement a fix.
Job ID: 67293922127
Job URL: https://github.com/github/update-project-action/actions/runs/23162076204/job/67293922127

---

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.

[Copilot]

Pull request overview

Adjusts the Jest test environment to avoid @actions/core.setFailed()’s side effect (process.exitCode = 1) causing CI failures when negative-path tests run.

Changes:

• Add a partial Jest mock for @actions/core that preserves real exports but replaces setFailed with a no-op jest.fn().

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

[Copilot]

core.setFailed() from @actions/core sets process.exitCode = 1 as a side effect. Negative test scenarios trigger this, causing jest to exit with code 1 even when all 33 tests pass — failing the CI test step.

Changes

• __test__/main.test.ts: Add a partial mock for @actions/core that replaces setFailed with a no-op jest.fn() while preserving real implementations of getInput, info, setOutput, etc. via jest.requireActual.

jest.mock("@actions/core",()=>({
...jest.requireActual("@actions/core"),setFailed: jest.fn(),}));

This prevents process.exitCode from being set during the test run, so jest exits cleanly with code 0 on a passing suite.

Original prompt

Fix the failing GitHub Actions workflow ci
Analyze the workflow logs, identify the root cause of the failure, and implement a fix.
Job ID: 67293922127
Job URL: https://github.com/github/update-project-action/actions/runs/23162076204/job/67293922127

---

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.

[Copilot]

Pull request overview

Adjusts the Jest test environment to avoid @actions/core.setFailed()’s side effect (process.exitCode = 1) causing CI failures when negative-path tests run.

Changes:

• Add a partial Jest mock for @actions/core that preserves real exports but replaces setFailed with a no-op jest.fn().

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

[Copilot]

core.setFailed() from @actions/core sets process.exitCode = 1 as a side effect. Negative test scenarios trigger this, causing jest to exit with code 1 even when all 33 tests pass — failing the CI test step.

Changes

• __test__/main.test.ts: Add a partial mock for @actions/core that replaces setFailed with a no-op jest.fn() while preserving real implementations of getInput, info, setOutput, etc. via jest.requireActual.

jest.mock("@actions/core",()=>({
...jest.requireActual("@actions/core"),setFailed: jest.fn(),}));

This prevents process.exitCode from being set during the test run, so jest exits cleanly with code 0 on a passing suite.

Original prompt

Fix the failing GitHub Actions workflow ci
Analyze the workflow logs, identify the root cause of the failure, and implement a fix.
Job ID: 67293922127
Job URL: https://github.com/github/update-project-action/actions/runs/23162076204/job/67293922127

---

📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.

[Copilot]

Pull request overview

Adjusts the Jest test environment to avoid @actions/core.setFailed()’s side effect (process.exitCode = 1) causing CI failures when negative-path tests run.

Changes:

• Add a partial Jest mock for @actions/core that preserves real exports but replaces setFailed with a no-op jest.fn().

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.