Improve PR CI workflow: readability, caching, and validation

[akshajtiwari]

Abstract

The current PR CI workflow (pr-check-tests.yml) is functionally correct but has several readability, maintainability, and minor performance concerns identified during review. Addressing these issues will improve long-term maintainability, reviewer clarity, and CI efficiency without changing the core behavior of the pipeline.

This issue proposes a targeted cleanup and enhancement of the existing workflow while preserving the original directory structure and intent.

---

Proposed Improvements

• Standardize section comment indentation and placement for better readability
• Remove redundant installation of ruff and black (already managed by pre-commit)
• Use working-directory consistently to improve clarity and reduce shell state reliance
• Simplify Python setup by removing the single-version matrix configuration
• Clarify PyInstaller’s role as a build-validation step, not an artifact delivery mechanism
• Add basic artifact existence checks after PyInstaller builds
• Extend pip caching to cover both the backend and sync microservice dependencies
• Add backend coverage reporting using pytest-cov

These changes do not alter the logical flow of the workflow and keep directory usage exactly as in the original design.

---

Expected Outcome

• Cleaner, more readable CI workflow
• Faster CI execution through improved caching
• Clearer intent behind build-related steps
• Better visibility into backend test health via coverage reporting
• Easier future extensions (e.g., additional Python versions, artifact uploads)

---

Scope

• File affected: .github/workflows/pr-check-tests.yml
• No changes to application logic or test behavior
• CI-only improvement

--

Pull Requests

I have made some changes and put up a Pull request for the same in #672 , commit akshajtiwari/PictoPy@d631a0e

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Related PRs

AOSSIE-Org/Resonate#479 - fix: resolve greet contributors workflow by moving to correct directory and adding reliability improvements [merged]
#449 - Rename workflows and setup Github secrets to generate builds [merged]
AOSSIE-Org/Resonate#496 - feat: add GitHub Action to auto-update project_structure.txt [merged]
AOSSIE-Org/Resonate#558 - feat: Added automated translation checker workflow [merged]
AOSSIE-Org/Resonate#581 - fix(ci) : Build and deploy workflow [merged]

👤 Suggested Assignees

• uju09
• vnaik10
• rahulharpal1603
• yuvikaaaaaa

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!

[akshajtiwari]

I would request to please assign this issue to me since I am already working on this

Check this commit for the changes I made akshajtiwari/PictoPy@d631a0e

[V4Vikaskumar]

Hi! I’d like to work on this CI workflow improvement.
I’ll focus on readability, caching steps, and validation enhancements without changing logical behavior.
Please let me know if there are any preferences for coverage reports or caching configs.

[akshajtiwari]

I have already pushed an update for the PR-test workflow (akshajtiwari@d631a0e) , however caching is required in other workflows as well and some more improvements too , you can have a look on them and review my changes as well if you wish to.