feat: add workflows to publish PR packages for testing#172
Open
arbrandes wants to merge 1 commit intoopenedx:mainfrom
Open
feat: add workflows to publish PR packages for testing#172arbrandes wants to merge 1 commit intoopenedx:mainfrom
arbrandes wants to merge 1 commit intoopenedx:mainfrom
Conversation
When a PR is labeled "package-pr", the CI workflow uploads the npm pack tarball as an artifact. A separate workflow_run-triggered workflow then attaches it to a GitHub release tagged pr-<number> and updates the PR description with the download link. A cleanup workflow deletes the release when the PR is closed. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
arbrandes
force-pushed
the
package-prs
branch
from
a6124e6 to
517939b
Compare
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
1 participant
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.
Description
When a PR is labeled "package-pr", the CI workflow uploads the npm pack tarball as an artifact. A separate workflow (required so that I can run in the upstream context, rather than the fork) then attaches it to a GitHub release tagged pr-[number] and updates the PR description with the download link. A cleanup workflow deletes the release when the PR is closed.
Consequences
There's no way to test this except to merge it to
main: it's a Github security restriction, for good reason. So this is what was done, and subsequently reverted with agit resetand subsequent force-push, so as not to pollute history. There's some remaining evidence from #171: the package creation log, and the corresponding cleanup log.Which is to say, it works. But not without side effects: for each PR package there is an actual Github release created. It is listed in the repo's releases page, and an automatic
git tagis created.LLM usage notice
Completed with assistance from Claude 4.6 Opus.