Please support the selection of a GitHub branch. Depending on the development process, you do not want to deploy the master branch.
As part of our upcoming re-brand of "Stitch" to "Realm" we'll also be migrating our feedback forum and joining the rest of MongoDB at feedback.mongodb.com, as part of that transition, we'll be shutting down this forum. We're still keeping track of this feedback and all of the related comments/discussions, but all future updates will be made here:
This improvement is now in progress.
Our development team has the same issue. We are using branches for deployment to staging/production on Heroku, Netlify and other services, but unfortunately Stitch does not support this method yet.
We do not want the production app to automatically deploy our development work without completed user acceptance testing on staging.
The current work-around for this issue (multiple repositories) is quite a manual operation and error prone. Two repositories holding the same code just for deployment purposes does not feel right as well.
Yes I have the same issue.
I have two different branches master and develop dedicated to different environments Test and Prod.
Test -> Develop -> App1
Prod -> Master -> App2
both are in single repository.