Skip to content
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

Add pipeline #2

Open
pavelsvagr opened this issue Aug 13, 2024 · 2 comments
Open

Add pipeline #2

pavelsvagr opened this issue Aug 13, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request

Comments

@pavelsvagr
Copy link
Member

Add pipeline that will publish the new version of the extension to Visual Studio Marketplace once merged to master

@pavelsvagr pavelsvagr assigned pavelsvagr and unassigned pavelsvagr Sep 3, 2024
@pavelsvagr pavelsvagr assigned rvfch and unassigned carishkaa Nov 28, 2024
@pavelsvagr pavelsvagr added the enhancement New feature or request label Nov 28, 2024
@smoliji
Copy link

smoliji commented Dec 6, 2024

Or keep the publish on manual release? I believe this is similar to what we do with NPM package publishing. I have this set up on healthz and I think we agreed it is a good approach: https://github.com/AckeeCZ/node-healthz/blob/master/.github/workflows/npm-publish.yml#L2-L4

@pavelsvagr
Copy link
Member Author

Yes, sorry, this was a wrongly worded issue. We want to keep the manual deploy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants