Fix GitHub Actions workflow error: Convert reusable workflow calls from steps to jobs #1002
+44
−15
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
The GitHub Actions workflow was failing with the error:
This occurred because the
optional-spec-validations.ymlworkflow was incorrectly trying to use thetask-failure-handler.ymlreusable workflow as step-level actions:Solution
GitHub Actions reusable workflows cannot be called as steps within a job - they must be called at the job level. This PR restructures the workflow to use the proper pattern:
jira_api_tokensecret to workflow definitions and ensured it's passed correctly from parent workflowsChanges
.github/workflows/optional-spec-validations.ymltask-failure-handler.ymlpostman-validation-error-handlerandipa-validation-error-handlerjira_api_tokensecret definition.github/workflows/release-spec.ymljira_api_tokensecret when callingoptional-spec-validations.ymlResult
The workflow now follows GitHub Actions best practices and will no longer fail with the "action.yml not found" error. All original functionality is preserved - failed validations still create GitHub issues and JIRA tickets for tracking.
Fixes the workflow execution while maintaining the same error handling behavior for optional spec validations.
Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.