Skip to content

Latest commit

 

History

History
34 lines (25 loc) · 1.14 KB

gdk_commands.md

File metadata and controls

34 lines (25 loc) · 1.14 KB

GDK commands

Update gitlab and gitlab-shell repositories

When working on a new feature, always check that your gitlab repository is up to date with the upstream master branch.

In order to fetch the latest code, first make sure that foreman for postgres is runnning (needed for db migration) and then run:

gdk update

This will update both gitlab and gitlab-shell and run any possible migrations. You can also update them separately by running make gitlab-update and make gitlab-shell-update respectively.

If there are changes in the aformentioned local repositories or/and a different branch than master is checked out, the make update commands will stash any uncommitted changes and change to master branch prior to updating the remote repositories.

Update configuration files created by gitlab-development-kit

Sometimes there are changes in gitlab-development-kit that require you to regenerate configuration files with make. You can always remove an individual file (e.g. rm Procfile) and rebuild it by running make. If you want to rebuild all configuration files created by the Makefile, run:

gdk reconfigure