WeWeb’s GitHub publishing functionality overwrites the entire branch root on every publish, which deletes custom GitHub Actions stored in .github/workflows. This prevents us from implementing automated deployment pipelines for our projects.
Impact
This is a business-critical limitation for our team. We cannot:
Automate deployments to staging/production environments
Run automated tests or quality checks on publish
Implement CI/CD pipelines that integrate with our existing infrastructure
Thanks so much for the detailed write‑up and for explaining how this affects your CI/CD setup, this is really helpful context.
I’ve passed your suggestions and questions on to the team so they can review options, and will update this thread as soon as there is any guidance or workaround that can be safely recommended.
Thanks a lot again for the detailed report and for walking through your CI/CD setup
At the moment, when WeWeb publishes to GitHub it overwrites the target folder in the branch, which means any existing .github/workflows inside that folder gets removed on each publish.
To avoid losing your workflows, the approach we recommend for now is:
Use your own repository root as the place for your code, config and GitHub Actions.
Configure WeWeb to publish its generated files into a subfolder of that repo instead of the root, for example:
One extra detail about the workflow files themselves:
Right now, the file uploader in WeWeb does not allow uploading files with a .yml extension directly.
As a workaround, you can upload your workflow as a .txt file (for example deploy-weweb.txt) in Project files, then click Set path and change its path/name to .github/workflows/deploy-weweb.yml before publishing.
After you save that path and publish, the file will appear in your repo under .github/workflows as a normal GitHub Actions workflow and GitHub will pick it up as usual.
I’m beginning to suspect that your proposed solution may have included some inaccurate information. My colleagues and I have searched through WeWeb but cannot find any way to do what you described:
In WeWeb, this means setting the publish path to something like weweb-output/ rather than the branch root.
Could you point us to where this setting is located? If it exists, this would resolve the issue completely. If not, it would mean WeWeb’s GitHub synchronization cannot be automated for deployment.
we don’t have the option to push the app to a subdirectory on GitHub
and the workaround of uploading the GitHub workflow files to the WeWeb app and pushing only the source files to GitHub doesn’t work at the moment.
We’ve added this to our backlog but the team needs a bit more time to figure out when we can add it to the roadmap proper.
In the meantime, Adrien on our team documented a workaround that should enable you to do automated deployment and leverage GitHub actions at the same time. You’ll need two repos:
