software-mansion / software-mansion/TypeGPU
chore: Rerun tree-shaking tests when a PR is updated
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3.2k
- Forks
- 122
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 34
Description
It seems like the tree-shaking test is run only once, when the PR is created, not on every change, making it stale.
Contributor guide
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
Inspect the pull-request workflow that runs the tree-shaking test and identify why it runs only when the PR is created. Update the workflow so changes to an existing PR rerun the test, then verify that the tree-shaking test is triggered after a PR update.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- ci-cd, testing
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100