Description
Currently, if the CLI runs a deployment and zero contracts are deployed, it still reports a success status. This is misleading because it usually means no deployments have been set up.
Expected Behavior
The CLI should not report success when no contracts are deployed. Instead, it should return an error or warning that clearly communicates the issue.
Proposed Improvement
-
Detect when no deployments are configured or executed.
-
Return a clear error message indicating that no deployments were performed.
-
Provide guidance for developers and agents on how to fix their setup, including:
- Using
config to add accounts.
- Assigning deployments to those accounts.
Why This Matters
Clearer errors help developers and agents quickly identify misconfigurations and avoid confusion when nothing is actually deployed.
Description
Currently, if the CLI runs a deployment and zero contracts are deployed, it still reports a success status. This is misleading because it usually means no deployments have been set up.
Expected Behavior
The CLI should not report success when no contracts are deployed. Instead, it should return an error or warning that clearly communicates the issue.
Proposed Improvement
Detect when no deployments are configured or executed.
Return a clear error message indicating that no deployments were performed.
Provide guidance for developers and agents on how to fix their setup, including:
configto add accounts.Why This Matters
Clearer errors help developers and agents quickly identify misconfigurations and avoid confusion when nothing is actually deployed.