playcanvas / playcanvas/editor
Be able to fork/export a project with all open branches
Open
Nobody has claimed this yet.
area: publishing
area: version control
enhancement
- Dominant language
- TypeScript
- Stars
- 1.3k
- Forks
- 215
- Avg merge
- 1d 29m
- Merged PRs (30d)
- 30
Description
There is a niche case where a project may need all it's branches to be forked/exported into another single project.
For example, if a project is targeting multiple portals or messengers (eg ad networks which all have slightly different requirements), they can have a branch per release portal.
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
The issue names no files, tests, or entry points. Start by locating the existing project fork/export flow and how branches are represented; confirm the expected behavior for exporting all open branches into one project, then add coverage for a project with multiple open branches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100