Conversation
Collaborator
|
I'm thinking if we should publish nightly build behind a tag. We can make it easy to update
|
Contributor
Author
|
I do that in svelte too, but both of those reps get a lot of PRs - this repo generally doesn't |
Collaborator
|
I'll set it up after next release. Doing a lot of changes. |
Collaborator
|
Did you create https://www.npmjs.com/org/shiki-bot? |
Collaborator
|
Feeling this would have unintended consequences — for example, I might have half-done changes on master that I want to polish before publishing. |
Contributor
Author
|
Cool, totally reasonable! |
This file contains hidden or 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
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.
This sets up GitHub to deploy packages when they change on a nightly basis. Sharing the infra with https://github.com/sveltejs/language-tools/
So for example, because I merged #51 today - then that package is the only one which would be deployed tomorrow morning
I don't have access to deploy the module, so I'm afraid adding the NPM access token in the security section - my recommendation is to make a shiki-only bot account to deploy so that your credentials don't go in there