My reasoning for this was to protect the main branch and to avoid accidental pushes of changes which may have the potential to break other users provisions.

As the config repo value is passed through verbatim via `Thor`, the following is possible when specifying a config repo.

```--branch people/username https://github.com/indieisaconcept/kitchenplan-config.git```

This provides scope for a user to then choose to merge changes into the master ( via a pull request ) or alternatively merge upstream changes into their branch.

The branch approach was an alternative to using submodules but I can revise to a normal commit, if you feel this would be more in-keeping with the direction you wish to take kitchenplan.