Use apropriate shop domain name in different environment

[rzaharenkov]

WHY are these changes introduced?

To standardize store domain normalization by using the shared normalizeStoreFqdn function from the CLI kit.

WHAT is this pull request doing?

Replaces the custom storeFullDomain utility function with the shared normalizeStoreFqdn function from @shopify/cli-kit/node/context/fqdn across store operations (copy, export, import). This ensures consistent handling of store domains throughout the codebase.

How to test your changes?

1. Run store commands with both full domains and shop handles:

  shopify store copy --from-store=my-store
  shopify store copy --from-store=my-store.myshopify.com

  SHOPIFY_SERVICE_ENV=local shopify store copy --from-store=shop2
  SHOPIFY_SERVICE_ENV=local shopify store copy --from-store=shop2.my.shop.dev

2. Verify all operations work correctly with both formats.

Measuring impact

How do we know this change was effective? Please choose one:

• n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes

[rzaharenkov]

• Use apropriate shop domain name in different environment #6123 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	78.06% (+0% 🔼)	12999/16653
🟡	Branches	72.28% (+0.02% 🔼)	6339/8770
🟡	Functions	78.17% (-0.01% 🔻)	3370/4311
🟡	Lines	78.46% (+0.01% 🔼)	12308/15686

Show files with reduced coverage 🔻

St.❔	File	Statements	Branches	Functions	Lines
🟢	... / info.ts	81.44%	61.19% (-1.49% 🔻)	90.32%	83.15%
🟢	... / ConcurrentOutput.tsx	98.36% (-1.64% 🔻)	92% (-4% 🔻)	100%	98.33% (-1.67% 🔻)

Test suite run success

3029 tests passing in 1311 suites.

Report generated by 🧪jest coverage report action from 51b40da

[github-actions]

We detected some changes at packages/*/src and there are no updates in the .changeset.
If the changes are user-facing, run pnpm changeset add to track your changes and include them in the next release CHANGELOG.

Caution

DO NOT create changesets for features which you do not wish to be included in the public changelog of the next CLI release.

[graphite-app]

Merge activity

• Jul 17, 2:04 PM UTC: This pull request can not be added to the Graphite merge queue. Please try rebasing and resubmitting to merge when ready.
• Jul 17, 2:04 PM UTC: Graphite disabled "merge when ready" on this PR due to: a merge conflict with the target branch; resolve the conflict and try again..