Trigger workflow when PR is marked ready for review

[satwiksps]

Description

This is a suggestion based on my personal experience to smooth out the contribution workflow. If this limitation is intentional (e.g., to save runner resources) or preferred by the maintainers, I am completely fine with rejecting the PR without merging

This PR updates the Continuous Integration (CI) workflow to automatically trigger when a Pull Request is converted from "Draft" to "Ready for Review"

Currently, the ci.yml workflow is configured to skip runs on Draft PRs which is fine. However, because the default pull_request trigger only listens for opened, synchronize, and reopened events, the CI pipeline ignores the ready_for_review event

So when a contributor marks a Draft PR as "Ready for Review," the CI does not run. Contributors are forced to push an empty commit (e.g., git commit --allow-empty) just to trigger the tests. This PR removes that friction to improve DX

Changes

• Modified .github/workflows/ci.yml to explicitly define pull_request trigger types
• Added ready_for_review to the list of types, ensuring the workflow captures the transition from Draft to Ready

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.54%. Comparing base (937efc2) to head (2549770).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1753   +/-   ##
=======================================
  Coverage   88.54%   88.54%           
=======================================
  Files         137      137           
  Lines       11515    11515           
=======================================
  Hits        10196    10196           
  Misses       1319     1319           

Flag	Coverage Δ
fast	82.09% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

[janfb]

absolute agree, this makes a lot of sense, thanks @satwiksps 🙌