Revision as of 01:01, 26 April 2023 view source Ellis Symons (talk \| contribs) Bureaucrats, Administrators 3,092 edits No edit summary ← Older edit		Revision as of 01:02, 26 April 2023 view source Ellis Symons (talk \| contribs) Bureaucrats, Administrators 3,092 edits →Workflow Newer edit →
Line 145: Once setup, the specific workflow will be dependent on how many many modellers will be working on the project concurrently and the specific goals of the project (e.g. are there going to be a lot of mitigation scenarios etc). The use of branches may be a robust approach in complex situations with a lot of mitigation options, or even a separate repository and GPKG for mitigation options.<Br> <Br> For the workflow, the easiest approach is to use something like Visual Studio Code for TUFLOW control file editing as this has a version control manager which will make the stage/commit/push/pull a lot easier and skips the need to be using the CLI. For kart, using the kart plugin in QGIS is the easiest method for skipping the need to use the CLI, however for ~~push~~pushing/~~pull~~pulling it may be necessary to use Git Bash to setup the SSH authentication. The TUFLOW plugin 'import empty' tool has an option to import directly into a kart repository, skipping the need to double handle the creation of TUFLOW GIS input files.

Kart Git And TUFLOW: Difference between revisions