diff options
| author | Jamie Hannaford <jamie.hannaford@rackspace.com> | 2017-06-15 14:25:20 +0200 |
|---|---|---|
| committer | Jamie Hannaford <jamie.hannaford@rackspace.com> | 2017-06-26 11:35:35 +0200 |
| commit | eab658607d41550c3cad7e7a83c7da3752a01eb9 (patch) | |
| tree | 509c18db30ff00ba16a9fdd4cf8126754055fd50 /generator/README.md | |
| parent | f3375f168e247c570d32e2b12639af671fa64ab9 (diff) | |
Add tests
Diffstat (limited to 'generator/README.md')
| -rw-r--r-- | generator/README.md | 22 |
1 files changed, 17 insertions, 5 deletions
diff --git a/generator/README.md b/generator/README.md index c522ec97..3fd2230e 100644 --- a/generator/README.md +++ b/generator/README.md @@ -1,14 +1,26 @@ # SIG Doc builder -This script will generate the following documentation files: +This folder contains scripts to automatically generate documentation about the +different Special Interest Groups (SIGs) of Kubernetes. The authoritative +source for SIG information is the `sigs.yaml` file in the project root. All +updates must be done there. + +When an update happens to the this file, the next step is generate the +accompanying documentation. This takes the format of two types of doc file: ``` -sig-*/README.md -wg-*/README.md -sig-list.md +./sig-<sig-name>/README.md +./wg-<working-group-name>/README.md +./sig-list.md ``` -Based off the `sigs.yaml` metadata file. +For example, if a contributor has updated `sig-cluster-lifecycle`, the +following files will be generated: + +``` +./sig-cluster-lifecycle/README.md +./sig-list.md +``` ## How to use |