publish VS Code extension on extensions marketplace

[zygoloid]

We should publish our VS Code extension for Carbon on the VS Code marketplace. We'll need to figure out what steps we need to follow here for publishing it and keeping it up to date.

[RohanVashisht1234]

I am ready to contribute:
I can transfer the ownership of my GitHub repository to carbon-language so that there is a base on which we can build carbon syntax highlighter further.

[zygoloid]

@RohanVashisht1234 If you can send us a PR to extend https://github.com/carbon-language/carbon-lang/tree/trunk/utils/vscode with your changes, that'd be ideal. Note that we do require that contributions follow our license rather than GPLv3.

With the newest version of VS Code, we can now provide a direct recommendation for use of our extension from within our own repository, without putting the extension on the marketplace: #3951 -- but that only addresses our own internal needs, not those of people using Carbon in other repos.

[RohanVashisht1234]

Sure, I am making the PR

[alienHuntrr]

Hello, I am a newbie. I am relatively new to open-source contributing. I saw this was a good first issue, so I came here. Is there anything I can contribute to?

[zygoloid]

The goal here is to have an official, published version of our VS Code extension on the marketplace. This is mostly a research project: find out what steps we need to follow to set up an official Carbon language account to publish extensions, how to go about publishing an extension, how we can automate that so we don't need manual effort periodically to keep it updated -- and then actually carrying out those steps :)

Given that we don't have a concrete list of things to do that we could walk a new contributor through here, I think I was wrong to label this as "good first issue", so I'm removing the label.

[visheshdembla]

hey @zygoloid, I can look into this one. I have previous experience with publishing VS Code Extensions.

[github-actions]

We triage inactive PRs and issues in order to make it easier to find active work. If this issue should remain active or becomes active again, please comment or remove the inactive label. The long term label can also be added for issues which are expected to take time.

This issue is labeled inactive because the last activity was over 90 days ago.