Best practices for version control and multiple developers

Best Practices post

I am trying to figure out how to best use DevKista with several developers. Currently, we are using git. We each make changes and push up to github which then pushes the files into a staging site on Kinsta. This is what I think @ZagnaH is suggesting in the post above. Is this still the best method for us to work together? The only change for us would be to move from Mamp Pro to Dev Kinsta.

I guess there isn’t an easy way to pull down changes from staging to keep things synced. The only benefit is to use DevKinsta to set up sites and be able to push to staging remotely.

Welcome to DevKinsta @mmcclard !

With multiple developers, I recommend using Git as well. With that in mind, perhaps don’t use the Push to Kinsta functionality of DevKinsta. Instead have a development flow that will push Git into Kinsta. We have a guide here on how to use Git with Kinsta.

Hey @michael, are there any plans to write a guide for How to use GitHub Actions with Kinsta?

Hi @Calvin_Harris. Welcome to DevKinsta! Not at this time, but I’ll let the team know there’s interest in that!

1 Like