Tracking Gisida Versions and Branches in Client Repos

Referencing: https://github.com/onaio/gisida/issues/428#issuecomment-586850390

We need to track which versions and branches our client repositories are using.

Gisida and Gisida React (public)

We should be able to run yarn install in the client repositories and install the correct versions / tags / branches. To do this let's maintain gisida and gisida-react as dependencies in the client package.json files.

// package.json
dependencies: {
  ...
  "gisida": "https://github.com/onaio/gisida#<branch/version/tag>",
  "gisida-react": "https://github.com/onaio/gisida-react#<branch/version/tag>",
   ...
}

Gisida React Private

Since this private repository is used as a submodule in client repositories, we can simply run:

git submodule init && git submodule update

to sync the submodule to the commit most recently checked into the client repository.

HOWEVER, this sets the local submodule git repo with a Detached HEAD, meaning further commits don't know where to push at origin, making it difficult to pick up and contribute.

Because of this I propose we start adding a comment in the clients' /src/index.js spelling out what branch is being used for the gisida-react-private repo.

Client Repositories

• Spotlight Zimbabwe (checked by: https://github.com/onaio/gisida/issues/428)
• Idai Recovery
• UNOPS (is this idai-recovery? a collection of repos?)
• Mesh2 (https://github.com/onaio/irfsomalia/pull/711)
• Service Mapping
• Nutrition Cluster
• Lotfa
• unicef-mozambique
• gisida-tonga
• gisida-solomon-isl
• gisida-yemen (already done)
• gisida-cambodia
• gisida-philippines
• UNICEF Indonesia
• ESARO
• UGAtlas
• Redss