Issues migrating site config at various points in project lifecycle
My colleague proceeded to install Drupal also, also a standard install, composer install, drush cr etc., and then pulled the latest changes and ran drupal ci and ran into an error, namely:


Don't do that. Config import/export is meant to be used for the same site. That's exactly why the site UUID check exists, that's to tell you that what you are trying to do doesn't work.

Either you need to sync the database or you need to use something like https://www.drupal.org/project/config_installer to install based on an existing set of configuration.

Usually the process is that content and configuration flow in opposite direction. You have your production site where new content is created, from time to time you want to sync the full DB down to your staging/development and then you have configuration changes that you are creating locally and then deploying to dev/staging/production.

See also presentations like https://events.drupal.org/vienna2017/sessions/advanced-configuration-management-config-split-et-al for example.