3.1 KiB

Raw Blame History

Fortress Forever (Source SDK 2013)

Git

We will be using the branching model laid out here: http://nvie.com/posts/a-successful-git-branching-model/

Never push to the master branch, it should only recieve merges from the develop branch or a hotfix branch (per release)
Merge any source-sdk-2013 changes into the develop branch (will probably have to deal with conflicts)
Only use rebase when you have unpushed local changes and someone else pushed changes to the corresponding remote branch; never rebase a remote branch (see this and this)
Only merge from the develop branch to a feature branch when absolutely necessary (important bugfix, etc); features should ideally be self-contained

Committing

Always make sure the code you are committing compiles
Try to commit features and changes separately, rather than 20 files at once. This means we can easily revert certain pieces if we don't like them, rather than going through manually to remove stuff
Be descriptive in your revision comments.
If you aren't sure you're doing something the best way, comment it in code and possibly comment ("First pass, needs cleaning up!" for e.g.)

Code

Syntax

Variable, Function, File Names and Directory Structure

TODO Decide on a naming convention
Always make variable and function names as descriptive as possible (if 'i' stands for 'currentPlayerIndex' then use 'currentPlayerIndex')

Adding/Removing Files

Solution and makefiles are no longer stored on the repo, they are generated using VPC. To add/remove files from the project, you must edit game/client/client_ff.vpc and/or game/server/server_ff.vpc files and then execute createallprojects(.bat) in the src/ directory. To remove a non-FF-specific file from the project (like HL2DM files), add exactly what you would to add the file (or copy the line from the .vpc that includes it), but put a - before "$File".

Documentation

DOCUMENTATION.md

For documentation of general Source engine things or of implemented features, commit to the develop branch. For each feature branch, document the in-development feature as it is worked on; the documentation will get merged along with the feature once it is complete.

Doxygen Inline Commenting

Note: only use Doxygen commenting as necessary (see section Variable, Function, File Names and Directory Structure)

To describe classes/functions/files (List of available @ commands):

/// Brief description. (optional)
/** Detailed description. 

    @param parameterName Description of the param
    @returns Description of the return value
*/

To describe member variables:

int var; ///< Detailed description of the member variable
         ///< and more if needed

3.1 KiB Raw Blame History