You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Code Quality] Add JSON Schema not constraints for mutually exclusive fields #14489
The schema documents mutually exclusive fields (branches/branches-ignore, paths/paths-ignore) in $comment fields but doesn't use JSON Schema's not constraint to enforce them automatically. This means schema validation tools won't catch these errors - only the compiler validates them at runtime.
Current behavior:
Schema comments document: "mutually exclusive with branches-ignore"
JSON Schema validation doesn't enforce this
Only compiler catches the error at runtime
Expected behavior:
JSON Schema validation catches mutually exclusive field usage
Errors caught earlier in development cycle (IDE, pre-commit hooks)
Suggested Changes
Add JSON Schema allOf + not constraints in pkg/parser/schemas/main_workflow_schema.json:
"Schema documents mutually exclusive fields in $comment fields but doesn't use JSON Schema's not constraint to enforce them... Schema validation tools won't catch these errors; only the compiler validates them at runtime."
Priority
Medium - Improves developer experience by catching errors earlier. Enhances schema validation coverage.
Activity
github-actions commentedon Feb 8, 2026
🍪 Issue Monster has assigned this to Copilot!
I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot agent.
The Copilot agent will analyze the issue and create a pull request with the fix.
Om nom nom! 🍪