Move example to files

[Cyberface]

We wanted to move the example config code to files in the repo.

This starts this process and provides an example how to link the
files to the documentation.

[Cyberface]

currently this example lives in examples/workflow/make_workflow.

I don't really like the name make_workflow so better ideas are welcome!

[coveralls]

Pull Request Test Coverage Report for Build 190

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 40.648%

---

Totals
Change from base Build 186:	0.0%
Covered Lines:	1067
Relevant Lines:	2625

---

💛 - Coveralls

[duncanmmacleod]

@Cyberface, why not just have these files live in /examples/workflow/, what's the motivation for the extra depth?

[Cyberface]

@duncanmmacleod because there could be multiple different workflow types. For example there is another type here: https://gwin.readthedocs.io/en/latest/command-line/gwin_make_inj_workflow.html

That I was going to put in after this

[duncanmmacleod]

@Cyberface, then why not just call the relevant file /examples/workflow/basic.ini and have the workflow with injections called /examples/workflow/injection.ini or similar. We don't need to use gwin.ini IMHO.

[Cyberface]

@duncanmmacleod I like have separate sub-directories to keep the examples really self contained. If you just have /examples/workflow/ then you would have multiple .ini files that are not all compatible with each other.

We need another person to settle this :)

[Cyberface]

@cdcapano we need your input

[cdcapano]

I'm fine with the sub-directory, but call it something more informative, like 'gw150914', instead of 'make_workflow'.