Update the postCommit hook godoc to reflect API
Formatting changed to read better in generated docs.
@@ -417,21 +417,21 @@ type SourceBuildStrategy struct {
//
// 1. Shell script:
//
-// BuildPostCommitSpec{
-// Script: "rake test --verbose",
+// "postCommit": {
+// "script": "rake test --verbose",
// }
//
// The above is a convenient form which is equivalent to:
//
-// BuildPostCommitSpec{
-// Command: []string{"/bin/sh", "-ic"},
-// Args: []string{"rake test --verbose"},
+// "postCommit": {
+// "command": ["/bin/sh", "-ic"],
+// "args": ["rake test --verbose"]
// }
//
-// 2. Command as the image entrypoint:
+// 2. A command as the image entrypoint:
//
-// BuildPostCommitSpec{
-// Command: []string{"rake", "test", "--verbose"},
+// "postCommit": {
+// "commit": ["rake", "test", "--verbose"]
// }
//
// Command overrides the image entrypoint in the exec form, as documented in
@@ -439,17 +439,17 @@ type SourceBuildStrategy struct {
//
// 3. Pass arguments to the default entrypoint:
//
-// BuildPostCommitSpec{
-// Args: []string{"rake", "test", "--verbose"},
+// "postCommit": {
+// "args": ["rake", "test", "--verbose"]
// }
//
// This form is only useful if the image entrypoint can handle arguments.
//
// 4. Shell script with arguments:
//
-// BuildPostCommitSpec{
-// Script: "rake test $1",
-// Args: []string{"--verbose"},
+// "postCommit": {
+// "script": "rake test $1",
+// "args": ["--verbose"]
// }
//
// This form is useful if you need to pass arguments that would otherwise be
@@ -458,9 +458,9 @@ type SourceBuildStrategy struct {
//
// 5. Command with arguments:
//
-// BuildPostCommitSpec{
-// Command: []string{"rake", "test"},
-// Args: []string{"--verbose"},
+// "postCommit": {
+// "command": ["rake", "test"],
+// "args": ["--verbose"]
// }
//
// This form is equivalent to appending the arguments to the Command slice.
