creates build and pr to gh-page

[psankhe28]

Checklist

• A link to the issue/user story that the pull request relates to
• How to recreate the problem without the fix
• Design of the fix
• How to prove that the fix works
• Automated tests that prove the fix keeps on working
• Documentation - any JSDoc, website, or Stackoverflow answers?

Issue/User story

Steps to Reproduce

Existing issues

• Stack Overflow issues
• GitHub Issues
• Discord history

Design of the fix

Validation of the fix

Automated Tests

What documentation has been provided for this pull request

[davidkel]

@psankhe28 I don't think this is what we will go with as discussed previously. So here is my suggestions

1. Submit a PR to the gh-pages branch that replaces the documentation with the new version of docs in the main branch
2. Write a section in the release_process.md file in main about how to add another version of the docs (for example v1.0.0) to gh-pages via a pull request. The instructions should set that to the default version (but ensure that the 0.6.0 version still remains) and it would then be submitted to gh-pages as a PR manually.

Investigating how mike works the whole of the gh-pages branch content will be managed by mike, therefore we can take a different approach to managing the content which still retains branch protection but allows github actions to automate publication without the need to generate PRs. This is not something that needs investigation at this time though so please don't look into it.

[davidkel]

We aren't going with a PR approach for github actions