test(command-build): don't run on forked repos

[erezrokah]

Build tests now require a valid auth token which is not available to forked PRs.
Fixes CI failures in #1758

[eduardoboucas]

What does this mean for external contributors that submit a PR? Are we able to run the tests "on our side" before merging?

[erezrokah]

What does this mean for external contributors that submit a PR? Are we able to run the tests "on our side" before merging?

We can run those tests locally and they'll run on the default branch post merge.
Contributors should also run those tests locally, but we don't have a good way (yet) to enforce tests that require GitHub secrets.
I'm planning on adding a mock API server as a part of #1489 (comment) so maybe we could fallback to a mock API on forks?

[eduardoboucas]

maybe we could fallback to a mock API on forks?

Sounds good. Until we get there, perhaps there's something we can do internally to ensure we don't merge a PR from a forked repo without running the test suite locally, because going forward the PR status will be misleading and there's nothing stopping us from merging a PR that actually breaks the build.

[erezrokah]

Sounds good. Until we get there, perhaps there's something we can do internally to ensure we don't merge a PR from a forked repo without running the test suite locally, because going forward the PR status will be misleading and there's nothing stopping us from merging a PR that actually breaks the build.

Good point. Let's continue this discussion in #1769