Given this is supposed to be used from GitHub action workflows (exclusively?), it doesn't seem necessary to tell all users to do npm install pkg-pr-new.
What if we could just add uses: stackblitz-labs/pkg.pr.new@v0 to a GitHub Actions workflow. e.g.
name: ci
on: [push, pull_request]
jobs:
run:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- run: npm install
- run: npm run build
- uses: stackblitz-labs/pkg.pr.new@v0Under the hood it could probably just do npx pkg-pr-new@latest anyway, but it'd mean that it'd be just one step to add to a repo - also you'd see that it's owned by stackblitz and therefore probably pretty safe to use.
Given this is supposed to be used from GitHub action workflows (exclusively?), it doesn't seem necessary to tell all users to do
npm install pkg-pr-new.What if we could just add
uses: stackblitz-labs/pkg.pr.new@v0to a GitHub Actions workflow. e.g.Under the hood it could probably just do
npx pkg-pr-new@latestanyway, but it'd mean that it'd be just one step to add to a repo - also you'd see that it's owned by stackblitz and therefore probably pretty safe to use.