I just had a question quick about how Drupal's config sync works. I work on a large Drupal site where I am having some coworkers joining in on working on the project. It's a version controlled site where we develop locally on Docker and then pull changes to a web server.
I recently discovered that Drupal has a "config synchronization" feature. If making changes to the site (be it views, blocks, etc.), a user can go to this page, export their configuration into a tar file, and import into their local setup (or vise versa, from dev to prod).
That much I have learned and is one way to sync Drupal environments. But I am confused as to how the config sync directory comes into play (the one with the UUID of the site that gets stored into the files directory by default). On a local dev environment on a test branch, I relocated this folder, version controlled it, and changed the settings.php to point to this new location. I noticed, when I make changes to anything (say a view), the config sync folder has no changes shown. If I go to the config sync screen, I then see this message:
The following items in your active configuration have changes since the last import that may be lost on the next import.
views.view.test_config_view
I'm very confused what the purpose of the config sync folder is. Is it not supposed to update somehow when changes are made to a Drupal site? I tried clearing the cache and everything. I thought this would be the correct way to synchronize changes with multiple people working on the site (instead of using the import/export screen and creating tar files). I'm also confused as to why it's forcing me to synchronize to the last import done, even if mine has more recent edits. Thank you for anyone who can better explain this to me.
