-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[request] adopt vscode-mpc under DOCGroup #180
Comments
What about transferring your repo to the @DOCGroup organization and we give you access there? |
Feel free to transfer it to me, I will transfer it to DOCGroup |
Transfer request sent. |
Acceptee, will transfer it to docgroup tomorrow |
Done |
Thanks. Does DOCGroup have an Azure DevOps organization (required to publish VSCode extensions to the marketplace…) yet? Or do you want me to create a personal one and publish it under that? |
We had something on azure devops for the pipelines, will have a look at that asap |
@jwillemsen Any luck? Should be simple enough to publish it to the VSCode Extensions Marketplace with an org personal access token. |
Can't easily find whether we have a DOCGroup organization on azure, probably not |
To ease debugging #177, I created a simple VSCode extension to basic support for MPC, which I pushed to vscode-mpc. This properly should live under the DOCGroup organization before being added to the VSCode extension marketplace. Could you please fork and adopt this repository?
The extension supports
.mpc
and.mwc
, and also a little bit of.mpd
files (code-folding in particular).The text was updated successfully, but these errors were encountered: