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
Currently CLI and hyp-deploy only do one actual origin at a time despite potentially deploying to multiple chains (because that's how the deployers in the SDK work).
I propose we replace the two-step origin + remotes selection in the CLI with a single chain multi-select step and assume they should all be interconnected.
The text was updated successfully, but these errors were encountered:
### Description
- Support multiple origins in PI deployments
- Simplify ci test with single core deploy command
- Improve output format of chains list command
### Related issues
Fixes#2813
### Testing
Tested locally and with e2e test
Currently CLI and hyp-deploy only do one actual origin at a time despite potentially deploying to multiple chains (because that's how the deployers in the SDK work).
I propose we replace the two-step origin + remotes selection in the CLI with a single chain multi-select step and assume they should all be interconnected.
The text was updated successfully, but these errors were encountered: