-
Notifications
You must be signed in to change notification settings - Fork 129
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
chore: auto publish alpha versions #1414
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Size Change: 0 B Total Size: 1.19 MB ℹ️ View Unchanged
|
pauldambra
added
the
release alpha
NB _when applied_ release an alpha version to NPM
label
Sep 12, 2024
pauldambra
commented
Sep 12, 2024
pauldambra
added
release alpha
NB _when applied_ release an alpha version to NPM
and removed
release alpha
NB _when applied_ release an alpha version to NPM
labels
Sep 12, 2024
pauldambra
added
release alpha
NB _when applied_ release an alpha version to NPM
and removed
release alpha
NB _when applied_ release an alpha version to NPM
labels
Sep 12, 2024
daibhin
approved these changes
Sep 12, 2024
pauldambra
added
release alpha
NB _when applied_ release an alpha version to NPM
and removed
release alpha
NB _when applied_ release an alpha version to NPM
labels
Sep 12, 2024
pauldambra
added
release alpha
NB _when applied_ release an alpha version to NPM
and removed
release alpha
NB _when applied_ release an alpha version to NPM
labels
Sep 12, 2024
pauldambra
removed
the
release alpha
NB _when applied_ release an alpha version to NPM
label
Sep 12, 2024
pauldambra
added
release alpha
NB _when applied_ release an alpha version to NPM
and removed
release alpha
NB _when applied_ release an alpha version to NPM
labels
Sep 12, 2024
pauldambra
added
release alpha
NB _when applied_ release an alpha version to NPM
and removed
release alpha
NB _when applied_ release an alpha version to NPM
labels
Sep 12, 2024
pauldambra
added
release alpha
NB _when applied_ release an alpha version to NPM
and removed
release alpha
NB _when applied_ release an alpha version to NPM
labels
Sep 12, 2024
pauldambra
commented
Sep 12, 2024
pauldambra
commented
Sep 12, 2024
pauldambra
removed
the
release alpha
NB _when applied_ release an alpha version to NPM
label
Sep 12, 2024
benjackwhite
requested changes
Sep 13, 2024
pauldambra
commented
Sep 13, 2024
benjackwhite
approved these changes
Sep 16, 2024
This was referenced Oct 11, 2024
This was referenced Oct 18, 2024
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.
Sometimes we want to test changes without releasing them generally
Let's allow ourselves to publish alphas more easily
This trigger type only fires if the workfllow file is on the default branch so I can't test it exclusively in one PR
This PR introduces a workflow file that runs when a specified label is added
The workflow
To Follow-up
it also isn't clever enough to e.g. push alpha-1, alpha-2 etc so if someone ran it twice on one version of posthog-js then it would fail but my goal today is to push an alpha of #1411 so I can figure out how to use it and then test it
to follow-up to this PR would then be detecting a sensible alpha version to publish