Update Hub content for renaming of 'Mkdocs Publisher' to 'Github Publisher'

[claremacrae]

See https://github.com/obsidianmd/obsidian-releases/pull/969/files

I believe that the update process will create a new plugin note, and the old one will be orphaned, so should probably be deleted by hand, once obsidianmd/obsidian-releases#969 has been approved, and then the Hub has been updated.

[lguenth]

I've looked into this... but since the plugin didn't change its ID, no new note was created and the old one still works as expected. Memo to myself that I should try to delete the old one, run the update_hub script locally and see if that changes the content.

[claremacrae]

Hi @lguenth,

I've looked into this... but since the plugin didn't change its ID, no new note was created and the old one still works as expected. Memo to myself that I should try to delete the old one, run the update_hub script locally and see if that changes the content.

There is a missing step in all this publishing, which is to run the update script with something like --overwrite to update existing files.

At the moment, running it (manually) generates a load of edits that need to be manually reviewed and lots reverted. I used to run it every couple of weeks but haven't done so for months.

From the last time that @argenos and I met to discuss work on the hub, I have some actions to enable the automation of this, but then I took over Tasks, and unfortunately haven't worked on the Hub code at all.

As an interim sticking plaster - and it's asking a lot - if you would be interested in running that update process periodically, we could screen-share and work through it, and document it...

[ooker777]

It now has been renamed to Enveloppe, with a new website https://enveloppe.github.io/. There is also Obsidian2Mkdocs in the inbox. I propose to rename it as Enveloppe, and merge obsidian-mkdocs-publisher to this one