Handle pytest “no tests collected” in Python application workflow

[Copilot]

The Python application / build workflow was failing on repositories with no Python tests because pytest exits with code 5 when nothing is collected. This change keeps that case non-fatal while preserving failure behavior for real test errors.

• Problem scope

  • CI failure was caused by pytest exit semantics, not by application/runtime errors.

• Workflow adjustment

  • Updated the test step in .github/workflows/python-app.yml to explicitly allow exit code 5.
  • Any other non-zero pytest exit code still fails the job.

• Behavioral impact

  • Prevents false-negative CI failures when test files are absent.
  • Does not weaken failure signaling for actual test failures.

- name: Test with pytest
  run: |
    pytest || test $? -eq 5

[Copilot]

Pull request overview

This pull request updates the Python CI workflow to treat pytest exit code 5 (“no tests collected”) as a non-failing outcome, preventing CI failures in repositories that don’t include Python tests.

Changes:

• Updated the pytest step to allow exit code 5 while still failing on any other non-zero exit code.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.