The issue has been successfully resolved. The AI agent made the following key changes to the workflow file:
Added a workflow_call trigger with an issue_number input, allowing the workflow to be called from external repositories.
Implemented a mechanism to set the ISSUE_NUMBER environment variable, which works for both direct triggers and workflow calls.
Updated all references to the issue number to use the new ISSUE_NUMBER environment variable.
These changes allow the workflow to be called from an external repository using the provided YAML code, resolving the original 'workflow_call key is not defined' error. The workflow is now flexible enough to handle both direct issue triggers and calls from other workflows.
This pull request fixes #133.
The issue has been successfully resolved. The AI agent made the following key changes to the workflow file:
workflow_call
trigger with anissue_number
input, allowing the workflow to be called from external repositories.ISSUE_NUMBER
environment variable, which works for both direct triggers and workflow calls.ISSUE_NUMBER
environment variable.These changes allow the workflow to be called from an external repository using the provided YAML code, resolving the original 'workflow_call key is not defined' error. The workflow is now flexible enough to handle both direct issue triggers and calls from other workflows.
Automatic fix generated by OpenHands 🙌