More scaffolder config cleanup

Signed-off-by: Tim Hansen <timbonicus@gmail.com>

docs/features/software-templates/configuration.md

@@ -18,17 +18,31 @@ The next step is to add
 [add templates](http://backstage.io/docs/features/software-templates/adding-templates)
 to your Backstage app.
 
-### GitHub
+### Publishing defaults
 
-For GitHub, you can configure who can see the new repositories that are created
-by specifying `visibility` option. Valid options are `public`, `private` and
-`internal`. The `internal` option is for GitHub Enterprise clients, which means
-public within the enterprise.
+Software templates can define _publish_ actions, such as `publish:github`, to
+create new repositories or submit pull / merge requests to existing
+repositories. You can configure the author and commit message through the
+`scaffolder` configuration in `app-config.yaml`:
 
 ```yaml
 scaffolder:
-  github:
-    visibility: public # or 'internal' or 'private'
+  defaultAuthor:
+    name: M.C. Hammer # Defaults to `Scaffolder`
+    email: hammer@donthurtem.com # Defaults to `scaffolder@backstage.io`
+  defaultCommitMessage: "U can't touch this" # Defaults to 'Initial commit'
+```
+
+To configure who can see the new repositories created from software templates,
+add the `repoVisibility` key within a software template:
+
+```yaml
+- id: publish
+  name: Publish
+  action: publish:github
+  input:
+    repoUrl: '{{ parameters.repoUrl }}'
+    repoVisibility: public # or 'internal' or 'private'
 ```
 
 ### Disabling Docker in Docker situation (Optional)