Fix test-coverage.yaml timeout caused by incorrect boolean expression

[Copilot]

The test-coverage.yaml workflow times out because the fail_ci_if_error parameter receives a string instead of a boolean value.

Changes

• Changed secrets.CODECOV_TOKEN to secrets.CODECOV_TOKEN != '' on line 43

Technical Detail

GitHub Actions secrets evaluate to their string value, not a boolean indicating existence. The expression secrets.CODECOV_TOKEN passes the actual token string (truthy) to codecov's fail_ci_if_error parameter, which expects a boolean. This causes the action to hang.

Before:

fail_ci_if_error: ${{ github.event_name != 'pull_request' || secrets.CODECOV_TOKEN }}

After:

fail_ci_if_error: ${{ github.event_name != 'pull_request' || secrets.CODECOV_TOKEN != '' }}

The corrected expression properly evaluates to boolean, allowing the workflow to complete.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>[Bug] test-coverage.yaml times out</issue_title>
<issue_description>test-coverage.yaml times out claiming that it needs a key</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes [Bug] test-coverage.yaml times out #44

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.20%. Comparing base (d1120b9) to head (1eca7e1).

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #45   +/-   ##
=======================================
  Coverage   91.20%   91.20%           
=======================================
  Files           7        7           
  Lines         853      853           
=======================================
  Hits          778      778           
  Misses         75       75           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.