Skip to content

Conversation

@ReWrite94
Copy link
Contributor

resolveModule was not passing the engine option from workflow overrides
or module config, causing workflows to fall back to default engine
instead of using the specified one.

This aligns resolveModule with resolveStep which already handles engine
correctly.

Should resolve #37

  resolveModule was not passing the engine option from workflow overrides
  or module config, causing workflows to fall back to default engine
  instead of using the specified one.

  This aligns resolveModule with resolveStep which already handles engine
  correctly.
@moazbuilds moazbuilds linked an issue Nov 28, 2025 that may be closed by this pull request
@moazbuilds moazbuilds merged commit b1347be into moazbuilds:main Nov 30, 2025
@moazbuilds moazbuilds added the bug Something isn't working label Nov 30, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

resolveModule() ignores engine parameter, defaults to Codex Engine option in resolveModule() is ignored - always falls back to Codex

2 participants