stackblitz-labs / stackblitz-labs/pkg.pr.new
GitHub Action?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 127
- PR merge metrics
- No merged PRs in 30d
Description
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@v0
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the proposed GitHub Actions workflow and the existing npx pkg-pr-new@latest entry point mentioned in the issue. Determine how the action should expose the same behavior through a uses: stackblitz-labs/pkg.pr.new@v0 step; done means a repository can use that step without separately installing pkg-pr-new.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100