lib/danger/ci_source/xcode_server.rb in danger-2.1.0 vs lib/danger/ci_source/xcode_server.rb in danger-2.1.1

@@ -1,22 +1,22 @@
 # Following the advice from @czechboy0 https://github.com/danger/danger/issues/171
+# https://github.com/czechboy0/Buildasaur
 
 module Danger
-  # https://github.com/czechboy0/Buildasaur
+  # ### CI Setup
+  #
+  # If you're bold enough to use Xcode Bots. You will need to use [Buildasaur](https://github.com/czechboy0/Buildasaur)
+  # in order to work with Danger. This will set up your build environment for you, as the name of the bot contains all
+  # of the environment variables that Danger needs to work.
+  #
+  # With Buildasaur set up, you can edit your job to add `bundle exec danger` as a post-action build script.
+  #
+  # ### Token Setup
+  #
+  # As this is self-hosted, you will need to add the `DANGER_GITHUB_API_TOKEN` to your build user's ENV. The alternative
+  # is to pass in the token as a prefix to the command `DANGER_GITHUB_API_TOKEN="123" bundle exec danger`.`.
+  #
   class XcodeServer < CI
-    ### CI Setup
-    #
-    # If you're bold enough to use Xcode Bots. You will need to use [Buildasaur](https://github.com/czechboy0/Buildasaur)
-    # in order to work with Danger. This will set up your build environment for you, as the name of the bot contains all
-    # of the environment variables that Danger needs to work.
-    #
-    # With Buildasaur set up, you can edit your job to add `bundle exec danger` as a post-actoin build script.
-    #
-    # ### Token Setup
-    #
-    # As this is self-hosted, you will need to add the `DANGER_GITHUB_API_TOKEN` to your build user's ENV. The alternative
-    # is to pass in the token as a prefix to the command `DANGER_GITHUB_API_TOKEN="123" bundle exec danger`.`.
-    #
     def self.validates_as_ci?(env)
       env.key? "XCS_BOT_NAME"
     end
 
     def self.validates_as_pr?(env)