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

Allows generating VSCode artifacts in branches #362

Merged
merged 1 commit into from
Feb 17, 2025

Conversation

ncordon
Copy link
Collaborator

@ncordon ncordon commented Feb 17, 2025

What

This PR allows us to trigger the workflow to archive VSCode artifacts in branches (PRs for example).

Up until now those artifacts were generated automatically but only on merging to main.

Why

So we can collaborate with the product department better on something getting merged to main

Copy link

changeset-bot bot commented Feb 17, 2025

⚠️ No Changeset found

Latest commit: 1f144a6

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@ncordon ncordon merged commit 473d0b0 into main Feb 17, 2025
4 checks passed
@ncordon ncordon deleted the allow-vscode-artifacts-from-branches branch February 17, 2025 15:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants