Better handling for merge error (conflicts), which can happen if we mess manually with the repo, deleting too much stuff, ...

[maxcmoi89]

Regarding this issue, I think it may be better to delete the local repo before each run of the publisher instead of keeping it.

Now it works like this:

1. Clone repo
2. Publish htacess
3. Publish htacess
4. Publish htacess

I think it would be better like this:

1. Delete repo folders
2. Clone repo
3. Publish htacess
4. Delete repo folders
5. Clone repo
6. Publish htacess

By opting for the second solution we always get a clean state of the git from the remote, which we update locally and push. Then we delete it again and ...
I believe this would fix a lot of errors related to merges, local changes, ... causing problems.
The process would be slower for very huge repos since we would download them each time with the clone, it would improve on a lot of merge issues though.