Solved: Do you use git topic branches with the Pantheon de... - Page 2

Report Inappropriate Content · 01-14-2016 03:37 PM

I love git and I'm used to the git flow and topic branches model. In this model any new changes are done on a new branch. You then create a pull request when your code is good and ready to merge into (master, develop or some other branch). Does this method work well with the Apigee developer portal as hosted by Pantheon?

From reading the current documentation, it seems to encourage people to just commit to master while they develop or fix bugs. In git that is not a best practice and usually discourage when working on teams.

williamking

I use our own git repo, as "origin", for branches, etc. I have the pantheon repo as my "upstream" and (usually) push to it from our own master once changes are merged.

Don't forget that Pantheon has three environments (dev, test, live) that your changes propagate through. So pushing to their master is only pushing to their dev environment, which you would then have to move through to live. It's not like pushing to master which is in turn hosting your production site.

View solution in original post

Do you use git topic branches with the Pantheon developer portal?