|
|
|
[Version Control](https://en.wikipedia.org/wiki/Version_control) is a Pro+ feature that seriously enhances developer workflow. If you're not a developer, don't worry about it.
|
|
|
|
|
|
|
|
Dulst can integrate with Git for version control.
|
|
|
|
|
|
|
|
There are 3 main integration points.
|
|
|
|
|
|
|
|
1. Commit. You can commit all current changes from your current Dulst game into the repository.
|
|
|
|
1. Checkout. You can check out any branch from the project into your current game. The game will match the branch exactly (with 1 exception), with any cards deleted in the branch being deleted in game. The one exception is the `/src/settings/basic.yml` file. The file controls the title, short-name, staff list, etc of your game. Checking out from the repo will never overwrite your game's basic settings. Basic settings will need to be manually setup and changed on a per-game basis with the Dulst interface.
|
|
|
|
1. Branch. You can create a new branch in the repo and this will create branching game of the game in Dulst at the same time. The new branch game will ONLY be able to push to that branch in the repo. The branch will exempt only `/src/settings/basic.yml` from being copied and the branch can be managed as an independent game.
|
|
|
|
|
|
|
|
Once a repo is set up, you can access your project on a web interface at [dev.dulst.com](dev.dulst.com). Powered by GitLab, it has the social code sharing and project management features you are already familiar with. You can also pull your repo to local once your keys are setup for fine control with command line or a GUI. I like [this GUI](https://git-fork.com/).
|
|
|
|
|
|
|
|
Version Control as a concept is the best way to allow multiple people to work on the same project with no conflicts. Each developer should create their own branch for each major improvement to the game they want to make. Once done, a merge request should be made to the main branch. Then the merge the changes into the main branch and finally checkout into the main game on Dulst. You can delete both the game and the branch in repo after.
|
|
|
|
|
|
|
|
The wiki is also controlled by the dev site.
|
|
|
|
|
|
|
|
Coming features:
|
|
|
|
|
|
|
|
Cards lists are not committed currently, this will be in future version.
|
|
|
|
Forums should be replaced with dev site's issues. |
|
|
\ No newline at end of file |
