Skip to content

fix(examples): use 'test' env consistently in Go Account scripts - #9714

Open
alia-bitgo wants to merge 1 commit into
masterfrom
aliaaamir/caas-2581-fix-go-account-env
Open

fix(examples): use 'test' env consistently in Go Account scripts#9714
alia-bitgo wants to merge 1 commit into
masterfrom
aliaaamir/caas-2581-fix-go-account-env

Conversation

@alia-bitgo

Copy link
Copy Markdown
Contributor

Summary

  • go-account-get-balance.ts and go-account-list-products.ts used env: 'staging', inconsistent with the rest of the Go Account example scripts which use env: 'test'. These scripts are client-facing and only test/prod are meaningful envs to them.
  • Updated the mainnet comment across all Go Account scripts to reference 'prod' (the canonical EnvironmentName) instead of the 'production' alias.

Test plan

  • Verify all examples/ts/go-account/*.ts scripts use env: 'test' by default
  • Confirm comments consistently say 'prod' for mainnet

Linear: CAAS-2581

🤖 Generated with Claude Code

go-account-get-balance.ts and go-account-list-products.ts used
env: 'staging', inconsistent with the rest of the Go Account example
scripts which use env: 'test'. These scripts are client-facing and
only 'test'/'prod' are meaningful envs to them.

Also updates the mainnet comment across all Go Account scripts to
reference 'prod' (the canonical EnvironmentName) instead of the
'production' alias.

TICKET: CAAS-2581
@alia-bitgo
alia-bitgo requested a review from a team as a code owner September 10, 2026 16:04
@linear-code

linear-code Bot commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

CAAS-2581

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant