feat(ci): continuous releases for main and PRs with pkg.pr.new #10369
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,35 @@ | ||
| name: Continuous Releases | ||
|
|
||
| on: | ||
| push: | ||
| branches: | ||
| - main | ||
| - docusaurus-v** | ||
| pull_request: | ||
|
|
||
| concurrency: | ||
| group: ${{ github.workflow }}-${{ github.head_ref || github.run_id }} | ||
| cancel-in-progress: true | ||
|
|
||
| jobs: | ||
| release: | ||
| name: Continuous Releases | ||
| runs-on: ubuntu-latest | ||
|
|
||
| steps: | ||
| - name: Checkout | ||
| uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1 | ||
|
|
||
| - name: Installation | ||
| run: yarn | ||
|
|
||
| - name: Build packages | ||
| run: yarn build:packages | ||
|
|
||
| - name: Fresh templates | ||
| run: | | ||
| yarn create-docusaurus fresh-examples/docusaurus-classic classic --javascript -p npm -s | ||
| yarn create-docusaurus fresh-examples/docusaurus-classic-typescript classic --typescript -p npm -s | ||
|
|
||
| - name: Release | ||
| run: npx pkg-pr-new publish './packages/*' --template './fresh-examples/*' --compact --comment=off | ||
|
There was a problem hiding this comment. I also turned off comments since there are many packages, but still, on each commit, we'll have the Continuous Releases check run.
When clicking details, we can see all the packages there without the need for a comment on each pull request. There was a problem hiding this comment. Thanks I think the comment is helpful for discovery, but it has to be more concise to be effective and only post the 2 template links. Until you have a better comment, it's preferable to hide it. |
||
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.
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.
We do not need installs, since templates would just be uploaded!
I also use npm here so we avoid that error, at least until I fix the issue with yarn in pkg.pr.new!
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.
Hmmm, wondering if generating a package-lock.json wouldn't be useful?
It looks like a tradeoff: resolve package versions ahead of time in CI vs letting the stackblitz user handle it. Maybe the DX will be better/faster for the end user if versions are already pre-resolved?