Guard missed test and document how to style

examples/simple_conduction/CMakeLists.txt

@@ -9,7 +9,8 @@ blt_add_executable( NAME        simple_conduction_without_input_file
                     OUTPUT_DIR ${EXAMPLE_OUTPUT_DIRECTORY}
                     DEPENDS_ON  serac_physics serac_mesh serac_functional
                     )
-if(ENABLE_TESTS)
+
+if(SERAC_ENABLE_TESTS)
     blt_add_test(NAME          simple_conduction_without_input_file
                  COMMAND       simple_conduction_without_input_file
                  NUM_MPI_TASKS 1 )

src/docs/sphinx/dev_guide/style_guide.rst

@@ -32,6 +32,24 @@ to one of ``A``'s instance variables ``Foo f``, ``B`` should store a non-owning
 either ``Foo&`` or ``Foo*``.  This should be ``const`` if at all possible.  In this case, shared ownership
 is not required because the lifetime of ``B`` is entirely dependent on the lifetime of ``A``.
 
+How to style your code
+----------------------
+
+We have two methods of enabling styling your code via ClangFormat. 
+
+The first method is to use the `style` build target on a configuration with the correct version of
+ClangFormat enabled. Here is an example on how to do it on LC's Ruby machine:
+
+.. code-block:: bash
+
+    $ ./config-build.py host-configs/[email protected]
+    $ cd [email protected]
+    $ make style
+
+The second method is to make a comment of ``/style`` on your open GitHub pull request. This will trigger
+a GitHub Action that will automatically style your code and commit it to your branch. You will need to
+`git pull` after it is finished to continue to work on that branch.
+
 Documentation
 -------------