Maintaining Your Fork

If you plan to run your own server using the LSB codebase, you'll want your own copy of the code repository. The best way to achieve this is to fork.

Creating your fork

GitHub provides an easy to use button in the top right of the front page of any repo, allowing you to create a full copy of the repo from that point in time. This copy will include all of the commit history and changes up to that point. This is important because your fork will have a shared history with the LSB codebase. This will allow you to easily cherry-pick code, or pull in feature branches from LSB.

Git Pull

Cherry-Picking

The command git cherry-pick <commit> applies the changes introduced by the named commit on the current branch. It will introduce a new, distinct commit. Strictly speaking, using git cherry-pick doesn’t alter the existing history within a repository; instead, it adds to the history. As with other Git operations that introduce changes via the process of applying a diff, you may need to resolve conflicts to fully apply the changes from the given commit. The command git cherry-pick is typically used to introduce particular commits from one branch within a repository onto a different branch. A common use is to forward- or back-port commits from a maintenance branch to a development branch.

Defensive Design

If you plan on making heavy modifications to the LSB codebase while still receiving changes from it, you will likely want to employ some defensive design techniques to make sure your changes are not overwritten by the incoming LSB changes.

• Keep changes in separate files. If you replace a function call with your own that you keep in its own file, you will have less possible sources of collision. If you keep your SQL changes in a file that is applied after the regular LSB update, you never have to resolve conflicts.

• Block comments. If you employ /* block */, --[[ block ]] comment style around large blocks you are commenting out, you will only have to resolve changes on two lines, rather than the entire block in question.

• Mark your custom changes so they are easy to spot. Marking a block with // Custom server X's stat calculations will make sure it's very easy to spot and maintain when you're resolving conflicts.

• Namespacing. If you're replacing logic in specific function calls, you could keep your custom work in a namespace. NewServer::GetRandomNumber() is very clearly specific to your server.

Dangers of Copy/Pasting

Understanding the LSB License