apollographql
Schema Checks with --background flag should ensure APOLLO_VCS_COMMIT env is not empty & integration is enabled
Description
With the new background flag (which we are very pleased there is a way to do async checks now), we ran into an issue where a team added the flag, but we never setup the integration on the account, so the check has been failing silently since they added it. It would have been helpful for any schema check run with the background flag to ensure that the env required for the github integration to work properly (APOLLO_VCS_COMMIT) was verified to be non null/empty before the check was run to avoid an improper setup.
As an extension to this, it would also be nice if there was some way for the schema check with the background flag running to ensure that the github apollo app is even installed to the account, but realizing that may be more complicated than just verifying an env, so understand if that is not a feature worth exploring.
