You do not want to push on save of files. You need to complete your changes
and then add, commit and push them.
You also want 2 remotes. So you push to the testing remote. Check the files
are ok and then you push to the live remote. Not push to testing which auto
pushes to live.
On Saturday, August 30, 2014 8:36:01 PM UTC+1, Artur Gabryś wrote:
> I would like to use Git while working on my website. Here's how it looks
> in my case:
> - I have a dedicated server
> - I have a website domain.com
> - I have a copy of this website at test.domain.com, I'm testing my
> changes at this test url. If everything is ok i send changed files to
> - I work on my local laptop
> It's very time consuming and the biggest problem is when I made changes
> and after couple of days I need to return to previous version of the file.
> I need to have version control software.
> I want to work with my website on my laptop, after saving files (or
> automatically during) they should be push to the test.domain.com and if
> everything would work OK I would copy file to domain.com.
> I don't understand how you should work with Git? Well I do but I think
> it's not right. Ok you make some changes to file (or someone else) and it's
> push to domain.com ? what if you made mistake in code and domain.com will
> crash? there have to be something in the middle, before user of your
> website will see your changes, right?
> Best regards,
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
For more options, visit https://groups.google.com/d/optout.