Updating SD.Next

Recommended procedure to update SD.Next to latest release is to simply
add command line arg: --update or --upgrade (they are aliases)

./webui.sh --update # linux/macos
webui.bat --update # windows
webui.ps1 --update # windows with powershell

Update under-the-hood uses standard git operations with some extras: - verifies status of core repo and performs auto-repair as needed
- updates core SD.next repo
- updates all built-in submodules
- synchronizes levels of all submodules

Manual Update

Instead of using automatic update using --update flag, you can update SD.Next manually using GIT:

git pull

Note

In case you have any git conflicts, you must resolve then before running git pull or otherwise it will fail

Note that in this case, you're updating only core repo
Additionally, check status of submodules:

git submodule status
git submodule update

Switching Branch

SD.Next development is done in multiple branches on GitHub:
- Stable branch: master
Typically updated every several weeks after latest features have been tested
- Development branch: dev
Updated regularly (e.g. daily) with latest features, fixes and changes
This branch always contains latest patches, but it is not fully tested
Once we decide on release schedule and consider it as sufficiently stable and tested,
code from dev is merged into master
- Feature branches:
For larger features we create additional branches as needed
Once feature work has completed, feature branch is merged to dev and removed

You can switch which branch of the SD.Next you are using at any point in time
You do not need a separate installation of SD.Next

git checkout master # to switch to master branch
git checkout dev # to switch to dev branch

Tip

Before switching branches, it is recommended to perform update

Warning

If differences between branches are significant, it may trigger installation of new requirements