Prevent plugins from generating environment-specific configs?

I’m developing locally and using local and staging environment configs. When I make changes to plugin settings through the admin panel while working in, say, localhost, the plugin saves its settings in user/localhost/config/plugins.

I realize that’s expected behavior, but is there any way to force them to save to the global config?

Ok, I think I answered my own question.

Be sure the user level config is correct then delete the environment level config:
user/localhost/config/plugins/some-plugin.yaml

Then use a relative symlink (previous version of this post did not use relative symlinks) to point the environment config to the user level config. For example, if the environment is localhost, starting from grav root:

cd user/localhost/config/plugins
ln -s ../../../config/plugins/some-plugin.yaml some-plugin.yaml