[Actions] Manually check which workflow is relevant to avoid bugs#259
Conversation
LuaGenerator ResultsNo changes detected. |
There was a problem hiding this comment.
Pull request overview
This PR updates several generator-related GitHub Actions workflows to determine “relevance” on pull_request synchronize events by querying the GitHub compare API, so expensive downstream jobs can be skipped when the latest pushed commit doesn’t touch the workflow’s target paths.
Changes:
- Replaced
dorny/paths-filterwith agh api repos/.../compare before...aftercheck to compute arelevantoutput. - Removed the
changesjob-levelif:so the job always runs and emitsrelevant(defaulting totruefor non-pull_request/non-synchronizeevents). - Simplified downstream job conditions to
if: needs.changes.outputs.relevant == 'true'.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| .github/workflows/ProxyStubGenerator.yml | Switches relevance detection to gh api compare and gates downstream jobs on relevant. |
| .github/workflows/PluginSkeletonGenerator.yml | Same relevance check change; gates Thunder/prepare on relevant. |
| .github/workflows/LuaGenerator.yml | Same relevance check change for Lua + ProxyStub paths; gates generation on relevant. |
| .github/workflows/JsonGenerator.yml | Same relevance check change; gates downstream jobs on relevant. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Plugin skeleton preview (latest run): No changes detected in generated plugin code. The PR changes are internal to the generator or do not affect output. |
JsonGenerator ResultsNo changes detected. |
No description provided.