Open mmkal opened 2 months ago
I'm thinking about this, it's solid, how can we handle options at that point? like compact, templates and projects?
how can we handle options at that point? like compact, templates and projects?
- uses: stackblitz-labs/pkg.pr.new@v0
with:
projects: 'packages/*'
template: foo
compact: true
comment: create
Or maybe keep it simpler:
- uses: stackblitz-labs/pkg.pr.new@v0
with:
args: 'packages/* --template foo --compact --comment=create'
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.Under 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.