add tests in `publish`

[kjaymiller]

In order to publish the site we have some custom code that builds the pages... This code isn't tested...

Should we test it?

• GH-Issues has tests and the other services being used (jinja2) have tests... the things that we could possibly test are

1. Do all the required paths exist? (Which the script would fail due to invalid paths)
2. Is all the information required in the issue? (Which we can make required fields)
3. Is the output path correct (this path should be a CONSTANT)

CC: @jonafato?

[jonafato]

Should we test it?

Definitely. I think your questions listed here all make sense. In terms of implementation, the only approach that comes to mind is to have some sample issue text that gets loaded (instead of a real issue) and runs the full process to create the site content markdown file and then do a test build of the site. Open to suggestions for other options, but I think we'll want to make sure that whatever the automation scripts produce results in a correctly build site.