Skip to content
This repository has been archived by the owner on Apr 8, 2020. It is now read-only.

Add support for skipping the self-export step #11

Open
colans opened this issue Feb 11, 2016 · 1 comment
Open

Add support for skipping the self-export step #11

colans opened this issue Feb 11, 2016 · 1 comment

Comments

@colans
Copy link

colans commented Feb 11, 2016

Currently, the destination's configuration is exported and committed before merging configuration from the source.

There are situations where this behaviour is not desirable, when the destination's database configuration is irrelevant/throw-away (say on a testing site) or the developer has already done an export and committed exactly what he/she wants from it.

So there are times when we only want to merge branch code on the destination with exported database configuration from the source, without needing anything from the destination's database.

As such, I'm proposing a --no-self-export option which, when provided, will skip the destination export and commit.

I'm working on this currently, and am planning to have a PR for this soon.

@colans
Copy link
Author

colans commented Jun 23, 2016

Perhaps this is no longer necessary now that there's a config-pull command. See drush-ops/drush#1711 for details.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant