How to set up website updates in Wordpress?

Question

WordPress

I read the advice in this thread . Organization of the technical process for developing the site (version control, testing, updating on the server)
Since we are dealing with layout, I will test manually.
Therefore, I would like to understand what to read in order to set up the Development -> Staging -> Production update system, (possibly Development -> Staging -> GIT -> Production.

If in detail, then files will be uploaded to Dev through PHP Storm, then I wanted I would like to transfer files from Development -
> Staging (having tried a bunch of plugins, like BackupBuddy, nothing works, constant errors), although there are useful functions, like tracking changes on the site. production.
But if you try to implement Staging -> GIT -> Production, then again there are questions, since I usually add files to GIT by hand. Is there any information on how to implement the automatic addition of files to GIT, so that later it could be rolled back if something happens.
Don’t hit me hard, I’ve been digging search engines for 4 weeks periodically, but in fact I could only find plugins that don’t work.

Answer 1

There is such a thing as VersionPress , the plugin itself is free. Haven't used it but looks promising. Also, Delicious Brains blog has a lot of information, in particular, they slipped through articles on the deployment of Wordpress sites. I can’t find the exact links now, but there were, look.
For myself, I organized this process in the form of a plugin for Composer in order to install Wordpress and plugins through it, so the deployment as a whole is not much different from other sites. Of course, it has its own specifics, but it often steers quite well due to wp-cli .

Answer 2

If the question is still relevant, see my answer here in this thread . You can learn something useful about the process.
In short - forget about all sorts of ftp and other old school. Working locally, commit and push to the desired branch. Further, on the side of the remote repository (GitHub, Bitbucket, Gitlab), all the magic happens, which you need to figure out once how to set it up (Travis CI, Jenkins, Bitbucket Pipelines, etc.). We pushed it into the develop branch - it was assembled automatically, tested and uploaded to staging. Smerdzhili in master - uploaded to prod. In addition, write scripts to automate other actions (synchronization of the database, media files, and God knows what else - it depends on the project and tasks).