Compromising local development with Playcanvas Editor

Hello,

I work for a company that uses Playcanvas as the backbone to our product. Lately we have been trying to improve our development pipeline, but we need some advice.

Before, we had been working entirely through the Playcanvas Editor, downloading the build through the rest API and then self hosting.

However, we were having problems with the integrated version control, and we wanted to move development to a bitbucket repository so that we could use Git, implement CI and testing, as well as improving our development pipeline for a growing team.

We set up a process in which we now have our main branch in bitbucket, and we are able to pull specific branches from the Playcanvas Editor to create bitbucket PRs and manage our merges directly in our repository. The catch is, we have not yet found a good way to then update our Playcanvas Editor branches to match what we have locally, needing to manually update our Editor main branch after each local bitbucket PR merge.

This leaves us with two options. Give up editor use entirely, or find a way to keep the editor project updated to match our bitbucket version. Ideally, we would like to maintain use of the Editor, but we need suggestions on how to make this pipeline work.

With all that in mind, my question is: Is there a way to update editor branches of a Playcanvas project to match local builds after local alterations? We have Playcanvas project to bitbucket project working, but we want the other direction if possible.

tl;dr: Is there a way to update a Playcanvas project from local builds, so that we can set up a Bitbucket to Playcanvas repo update pipeline, so that we can work locally while keeping use of the Editor?

1 Like

If you’re looking for a way to upload local code to the backend (Editor), you can look at: