main.yaml's validate job calls ci.yaml as a reusable workflow, running both Test and Validate Commit Subjects post-merge. The commit-subject check only makes sense pre-merge (should this PR be mergeable) - the commits are already merged by the time main.yaml runs, so re-checking their subjects is meaningless. Test should still re-run post-merge (verifies the actual merge result); commit-subject validation shouldn't.
main.yaml's validate job calls ci.yaml as a reusable workflow, running both Test and Validate Commit Subjects post-merge. The commit-subject check only makes sense pre-merge (should this PR be mergeable) - the commits are already merged by the time main.yaml runs, so re-checking their subjects is meaningless. Test should still re-run post-merge (verifies the actual merge result); commit-subject validation shouldn't.