1 vote2 comments · Service Improvement » Server Configuration Improvements · Flag idea as inappropriate… · Admin →
Thanks, Harry, for taking the time to report this.
I’d like to better understand your use-case in order to figure out what’s going on.
For example, if I have a git repository deployed on my server on Cloudways, and if I go ahead and delete an already tracked file from the repository on my local computer and push the changes upstream to the remote repository and then pull those changes on my Cloudways server, I do see that the deleted file is gone from my public_html/ (or any other deployment) directory. Are you having trouble with that?
Or is your workflow different from what I’ve described? Please let me know so I may check it thoroughly.
Cloudways TeamJustin Moh commented
Hi, this issue is very easy to be replicated -- might not the same, but close enough.
1. Deploy with your git repository
2. Push a commit
3. Pull the repository on Cloudways
4. `git reset --hard xxxxxxx` (you accidentally pushed credentials) and push the new commit
5. Pull the repository on Cloudways
6. Look in to the file content of that modified file : doomed.