...
You can export config via the admin interface or by using drush. In most cases, it is more efficient to use drush.
| Exporting config changes for a Pull Request | ||
|---|---|---|
| Via the Admin Interface | Using Drush | |
| 1 | Make database changes (e.g. change permissions) | |
| 2 | Create a new feature branch git checkout -b feature-branch-name | |
| 3 | Visit /admin/config/development/configuration/full/export and click "Export" |
|
| 4 | Uncompress the .tar.gz file system downloaded, and copy the config to your config directory | drush already exported the files where they need to go |
| 5 | If any of your changes are covered by config split, visit /admin/config/development/configuration/config-split and export the required config | drush exports config splits at the same time |
| 6 | Add the config changes needed for your PR. Do not check in changes unrelated to your feature. i.e. git add permissions.yml | |
| 7 | commit your changes git commit -m "Update author permissions to enable something" | |
| 8 | Push your changesgit push origin feature-branch-name | |
| 9 | Open a pull request from your feature branch | |
Loading Config Changes
You'll want to import new config changes to the database when you bring down new config changes through git. To do this:
...