codesandbox / codesandbox/codesandbox-client
[feature request] config to publish on branch too
Open
Nobody has claimed this yet.
🤔 Improvement
CodeSandbox CI
- Dominant language
- JavaScript
- Stars
- 13.6k
- Forks
- 2.4k
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 2
Description
🌈 Feature
I'd like to publish on master/main branch too.
Sometimes, I just push directly without PR, but I don't want to publish to npm even with beta/canary tag.
A new option to config when should publish, PR only or PR + all branches, or PR + specific branches
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
No files, tests, or entry points are named. Start by locating the publish configuration and the logic that distinguishes pull requests from branches; done means users can choose PR-only, PR plus all branches, or PR plus specified branches without unintended npm publication.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100