Open ghost opened 4 years ago
sounds possible.
what bcim
really needs to do is leverage the Backdrop config import api to run the necessary DB ops as well: https://github.com/backdrop-contrib/backdrop-drush-extension/issues/162
right now bcim
is strictly a file system operation which is great compared to nothing, but if you add a new field to a content type for example Backdrop will not know about that.
I think if bcim
leveraged the Backdrop API it would not move the README.md, but I'd need to check that.
that being said, i'm not opposed to trying to fix this if it is easier then #162 as an interim stop gap.
I'm working on B.org and when I import config from staging, I get a new README file in
dev-active
. It's the README from thestaging
directory (so it's contents don't make sense when read from thedev-active
directory). I have to just remove it before committing changes, but it'd be nice if instead drush'sbcim
only copied config files over (e.g.*.json
). Would that be possible?