Add the Wiki to version control with GH action to publish to Wiki?

[yorkshire-pudding]

Currently updating the wiki is a separate action to making a change to commands and relies on someone remembering to do it. My proposal is to add the wiki to the repo with a GitHub action to publish to the wiki area when merged.

Pros

• Allows wiki changes to be drafted as part of a pull request
• Wiki can be drafted using an IDE which will be more user friendly than the edit window for long pages.
• Less likely to forget to do wiki changes after the merge if need to be done at the same time
• Ties documentation changes to changes in commands, behaviour, or the API so the docs in a given version installed would match the functionality in that version.
• Would make it easier to add screenshots to the wiki as could have subfolder for images
• Some anecdotal evidence that locked down wikis can be indexed by Google, although we need a few more stars

Cons

• Would need to lock down the wiki as any changes made on the wiki screen would be lost on the next merge. There have been no wiki edits by people who wouldn't know how to do a PR so I'm not sure this would be a problem.
• Different workflow may take a bit of getting used to (I don't think any other backdrop projects do this)

The GH action I've found which seems to work well is: https://github.com/Andrew-Chen-Wang/github-wiki-action.

Thoughts?