ci: optimize workflows

[yacosta738]

This pull request significantly improves the CI workflow by making job execution more efficient and accurate through enhanced change detection and conditional logic. It introduces new change filters, optimizes job dependencies, and ensures that jobs only run when relevant files are modified. Additionally, it improves caching for Node.js dependencies and refines the handling of markdown and meta file changes across multiple workflows.

CI Workflow Enhancements:

• Added new change filters (docs, meta, secrets, webapp) in .github/workflows/ci.yml to more precisely detect changes in documentation, meta/configuration files, secrets, and webapp-related files, enabling finer-grained job triggering. [1] [2]
• Updated job dependencies and conditional execution so that linting, verification, and build/test jobs only run when relevant files have changed, reducing unnecessary CI runs and improving feedback accuracy. [1] [2] [3] [4] [5] [6]
• Refined the logic for checking lint and verification results, ensuring jobs are only required to succeed when their corresponding file types have changed, and providing clearer warnings when job statuses are unexpected. [1] [2]

Performance and Developer Experience:

• Improved caching of Node.js dependencies by specifying cache-dependency-path: "pnpm-lock.yaml" in all relevant jobs, which helps speed up CI runs and ensures consistent environments. [1] [2] [3] [4] [5] [6] [7]
• Added conditional execution for Docker-related steps in the backend pipeline, so Docker setup and warm-up only occur when PDF-related files change, further optimizing resource usage. [1] [2] [3]

Other Workflow Improvements:

• Updated the link checker workflow to only run on changes to markdown files, reducing unnecessary checks.
• Modified the Qodana code quality workflow to ignore documentation files, preventing irrelevant code quality checks on docs-only changes.

[coderabbitai]

Warning

Rate limit exceeded

@yacosta738 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 0 minutes and 38 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch ci/optimize-workflows

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

📝 [actionlint] _{reported by reviewdog 🐶}
shellcheck reported issue in this script: SC2086:info:12:8: Double quote to prevent globbing and word splitting [shellcheck]

[github-actions]

📝 [actionlint] _{reported by reviewdog 🐶}
shellcheck reported issue in this script: SC2086:info:12:8: Double quote to prevent globbing and word splitting [shellcheck]

cvix/.github/workflows/release.yml

Line 145 in 8d80b5e

run: |

[github-actions]

✅ Contributor Report

User: @yacosta738
Status: Passed (12/13 metrics passed)

Metric	Description	Value	Threshold	Status
PR Merge Rate	PRs merged vs closed	89%	>= 30%	✅
Repo Quality	Repos with ≥100 stars	0	>= 0	✅
Positive Reactions	Positive reactions received	9	>= 1	✅
Negative Reactions	Negative reactions received	0	<= 5	✅
Account Age	GitHub account age	3025 days	>= 30 days	✅
Activity Consistency	Regular activity over time	108%	>= 0%	✅
Issue Engagement	Issues with community engagement	0	>= 0	✅
Code Reviews	Code reviews given to others	343	>= 0	✅
Merger Diversity	Unique maintainers who merged PRs	3	>= 0	✅
Repo History Merge Rate	Merge rate in this repo	0.9156626506024096	>= 0	✅
Repo History Min PRs	Previous PRs in this repo	174	>= 0	✅
Profile Completeness	Profile richness (bio, followers)	90	>= 0	✅
Suspicious Patterns	Spam-like activity detection	1	N/A	❌

---

_{Contributor Report evaluates based on public GitHub activity. Analysis period: 2025-02-07 to 2026-02-07}

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[sentry]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[github-actions]

Qodana for JVM

156 new problems were found

Inspection name	Severity	Problems
Invalid @ConfigurationProperties	🔴 Failure	1
Invalid YAML configuration	🔴 Failure	1
Unused symbol	🔶 Warning	53
Invalid YAML configuration	🔶 Warning	49
Unresolved reference in KDoc	🔶 Warning	5
Taint analysis	🔶 Warning	4
Potentially ambiguous 'kotlin.coroutine.coroutineContext' usage	🔶 Warning	4
Unused import directive	🔶 Warning	1
Redundant character escape	🔶 Warning	1
Vulnerable declared dependency	🔶 Warning	1
Duplicated code fragment	◽️ Notice	12
Unknown HTTP header	◽️ Notice	10
Redundant interpolation prefix	◽️ Notice	4
Vulnerable declared dependency	◽️ Notice	3
Multi-dollar interpolation can be used in string literals (available since 2.1)	◽️ Notice	1
Redundant escaped dollar characters in string literals	◽️ Notice	1
String concatenation that can be converted to string template	◽️ Notice	1
If-Null return/break/... foldable to '?:'	◽️ Notice	1
Redundant empty initializer block	◽️ Notice	1
Unnecessary type argument	◽️ Notice	1
'substring' call should be replaced with 'take' call	◽️ Notice	1

☁️ View the detailed Qodana report

Contact Qodana team

Contact us at qodana-support@jetbrains.com

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions