-
Notifications
You must be signed in to change notification settings - Fork 20
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
Publish VSCode Extension to the Marketplace #142
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Deploying with
|
Latest commit: |
5865ce0
|
Status: | ✅ Deploy successful! |
Preview URL: | https://3176c82b.taqueria.pages.dev |
|
|
|
|
|
d8d8b73
to
5865ce0
Compare
|
GImbrailo
approved these changes
Jan 26, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@danielelisi This LGTM.
5865ce0
to
de91d1c
Compare
|
I've added a condition to this pipeline to trigger only if files inside
|
GImbrailo
pushed a commit
that referenced
this pull request
Jan 26, 2022
* Fix publishing job for VSCode Extension * Trigger workflow only if vscode extension code is changed
GImbrailo
added a commit
that referenced
this pull request
Jan 27, 2022
* chore: renamed build-and-test to build-binaries * chore: add npm build packages * chore: added npm scripts and publish jobs * chore: fixed duplicate job ids * chore: moved update package.json to npm script * chore: added plugin list outputs * chore: added plugin variable to update commad * chore: added node actions to release * chore: added checkout to release * chore: moved checkout and changed conditions for publish * chore: changed suffix output * chore: added --registry to npm publish * chore: added node token * chore: fixed npm publish command * chore: seperate npm publish from release * chore: seperate npm publish from release * chore: removed teztnets * chore: removed flextesa * chore: removed redundant build job * chore: try npm version * chore: try npm version * chore: try npm version * chore: try npm version * chore: added access to public * chore: npm publish jobs * chore: added global env variables * chore: changed scope to taqueria * chore: changed tag for PR * chore: changed tag for PR * chore: updated website packages * chore: changed binary name to taq * chore: removed custom npm scripts * chore: removed windows and mac binaries until merge * chore: try merge comment jobs in one * chore: try merge comment jobs in one * chore: cleanup environment variables * chore: change npm version * chore: change npm version * chore: GITHUB_SHA env expression * chore: short sha in javascript * chore: short sha in javascript * chore: fix comment tag * chore: add line break * chore: add line break * Automatically run npm install before running npm run build * Update .gitignore for vscode-extension * Update .gitignore * Taqueria vscode initial commit * Initial init command * Rebase branch on latest changes from main * VSCode Extension pipeline for testing, building, and publishing * fix string interpolation * set default working-directory * Fix typo on output * remove working-dir default * add file extension * chore: update README warning * Publish VSCode Extension to the Marketplace (#142) * Fix publishing job for VSCode Extension * Trigger workflow only if vscode extension code is changed * chore: publish next and latest if release is published * chore: fixed next check * chore: fixed package-lock.json for protocol * chore: using scope env variable Co-authored-by: Michael Weichert <mweichert.com> Co-authored-by: Daniele Lisi <22307776+danielelisi@users.noreply.github.com> Co-authored-by: Simon Boissonneault-Robert <simrob7000@gmail.com> Co-authored-by: Jev Björsell <jev@ecadlabs.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #97
PR #132 was merged early without going through code review so please feel free to review the entire pipeline.
Description
This PR and #132 create a pipeline for linting, testing, building, and publishing the VS Code Extension to the VS Code Marketplace.
Now that Taqueria repo is public I'm running the lint and test job on Windows and MacOS as well.
Test Plan
The pipeline succeed and the extension is successfully published to the marketplace.
VS Code Marketplace Link: https://marketplace.visualstudio.com/items?itemName=ecadlabs.taqueria