Skip to content

Conversation

jdblischak
Copy link
Contributor

@jdblischak jdblischak commented Sep 3, 2025

I noticed that in my previous PR to fix a minor formatting typo that a lot of CI was run (#7276). To reduce the required resources and also increase the speed of development, I added some more path-based filters to the GitHub Actions workflow triggers. Specifically:

  • Only run rchk if a file in src/ is updated
  • Only run coverage if a file in inst/tests/, R/, src/, or tests/ is updated

I also added the manual trigger workflow_dispatch. This is convenient when preparing a PR. As a developer, I can manually run a workflow on my feature branch in my feedstock (ie not the master branch), prior to opening the PR.

I didn't add any path filters to code-quality.yaml or R-CMD-check.yaml so that a baseline of CI is still run for every PR, but I could add them if requested.

Copy link

codecov bot commented Sep 3, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.01%. Comparing base (6e63f5b) to head (51bb553).
⚠️ Report is 23 commits behind head on master.

Additional details and impacted files
@@           Coverage Diff           @@
##           master    #7280   +/-   ##
=======================================
  Coverage   99.01%   99.01%           
=======================================
  Files          81       81           
  Lines       15503    15503           
=======================================
  Hits        15351    15351           
  Misses        152      152           

☔ 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.

@jdblischak
Copy link
Contributor Author

Thank you for the reviews @jangorecki and @Anirban166. Are there any additional steps you would like me to take before merging this PR?

@jangorecki
Copy link
Member

Probably nothing, it is waiting for someone who has commit rights and feels fine to take responsibility for fixing problems if something will go wrong...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants