Christopher Schleiden

Okay, thanks for the information. The difference between the editors is most likely because the MD extension has to be hosted in an iframe while the native editor is not....

Yes, we need to escape the filename when inserting, like: https://markdown-it.github.io/#md3=%7B%22source%22%3A%22%5Blink%5D%28http%3A%2F%2Fwww.bing.com%2F%5C%5C%20test%2F%29%5Cn%5Cn%5Blink%5D%28http%3A%2F%2Fwww.bing.com%2F%20test%2F%29%22%2C%22defaults%22%3A%7B%22html%22%3Afalse%2C%22xhtmlOut%22%3Afalse%2C%22breaks%22%3Afalse%2C%22langPrefix%22%3A%22language-%22%2C%22linkify%22%3Atrue%2C%22typographer%22%3Atrue%2C%22_highlight%22%3Atrue%2C%22_strict%22%3Afalse%2C%22_view%22%3A%22html%22%7D%7D

That makes sense, we'll take a look at the popup. Thanks for reporting and providing context!

There is an existing issue for supporting workspaces and in general more complex folder structures: https://github.com/cschleiden/vscode-github-actions/issues/17 but this would require some bigger changes to the UI, I'm not sure how...

@robert-spring do you have more information of your concrete scenario? Are you using a workspace?

I _think_ both extensions should be able to contribute auto-complete options. Do you see any output in the `GitHub Actions` Output window?

We have made some improvements, please try again and if you're still seeing errors open an issue in https://github.com/github/vscode-github-actions/issues

Thank you for this proposal 🙇 and sorry for the delay so far. I'll take a look in a bit!

Thanks for submitting this. Overall the approach makes sense to me. I think eventually we'd have to find a different approach to getting the starter workflows, when testing the branch...

If you have the right permissions for the repository, the extension does pull down the custom labels and also validates them:  Currently this only...