Add MyST-Markdown

[rtbs-dev]

Based on discussion here

[rtbs-dev]

Based on the link above, the maintainer of MyST-Markdown was seeking support/PR's to publish on Open-VSX.

@chrisjsewell This PR would add MyST-Markdown to open-vsx, resolving Issue#33. I think the devs here generally prefer the maintainers add their own extensions directly, but if you are ok with this it should work fine.

[chrisjsewell]

Fine by me thanks 👍

[rtbs-dev]

Fine by me thanks +1

Cool. For the future, if you want to manage both publishing to Marketplace and Open-vsx on the same toolchain, see this from another group asking to add to open-vsx. They link a github action they use to do both when a tag is published, which might be nicer.

[filiptronicek]

Hey there @tbsexton & @chrisjsewell, I'm happy that you want to add the extension to OpenVSX. In this repo, we try to minimize the number of extensions (we have 400+ currently) so that the jobs are quicker, it's easier to maintain and the extension authors know right away when something goes wrong.

The setup is pretty easy with GitHub Actions, so if someone wants to try implementing it, you can follow this guide with this template (both still a bit WIP) and ping me if there are any difficulties. If necessary, I can also contribute the PR myself, I'd be delighted to help 🙂.

[akosyakov]

@filiptronicek looks like PR is welcomed: executablebooks/myst-vs-code#33 (comment)

[rtbs-dev]

@filiptronicek if you start a PR to address executablebooks/myst-vs-code#33, I can see if I can help fill in some blanks.

[filiptronicek]

@filiptronicek if you start a PR to address executablebooks/myst-vs-code#33, I can see if I can help fill in some blanks.

Just raised executablebooks/myst-vs-code#37