If I've understood correctly, rather than pushing specific commits it might be better to have the developers working on feature branches and those features only get merged into a development/integration branch when they're ready for release. Then you would push the development/integration (or a release branch created from integration/development) from DEV to TESTING and then from TESTING into PRODUCTION for actual release.
It might help if you describe the branching process you follow between the DEVELOPERS and DEV repo as that might influence what you push into TESTING, PRODUCTION, etc. Probably pushing specific commits will end up in problems although I could be wrong and other's may disagree with me. On Friday, May 24, 2013 2:33:24 PM UTC+1, Bruno Cassol wrote: > > Hi, > we have the following setup and I would like advice/help. I'm not even > sure if this the correct setup. > > DEVELOPERS WORKSTATIONS (Windows/TortoiseGit) > c:\xamp\htdocs\intranet/ > | > | push / pull > V > DEV (CentOS/ssh) > /home/git/repos/intranet/ (bare) > /var/www/html/intranet/ (working/apache) > | > | push > V > TESTING (CentOS/ssh) <--- Boss tests the system here > /home/git/repos/intranet/ (bare) > /var/www/html/intranet/ (working) > | > | push > V > PRODUCTION (CentOS/ssh) > /home/git/repos/intranet/ (bare) > /var/www/html/intranet/ (working) > > > How can I only push some commits and not others from DEV to TESTING? > I also have to think about automating MySQL schema changes. We use PHP > (Zend framework) and MySQL. > Is there a better approach? > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
