Hello,
We decided to allow the entire repository to be tracked to allow for complete backups & restore points of a website if so desired.
Another major benefit is that you could perform a major core/plugin upgrade on a new branch without affecting the main branch/production website. Since Revisr allows you to optionally keep a separate version of each branch, you could test out a core upgrade on a new branch and switch back if it causes any issues, and not have to worry about the differences in the database.
However, you have the ability to add files or entire directories to the gitignore through the plugin settings page.
This way, if you want to track the entire repository, or just themes/plugins, you can.
As mentioned in this thread, you could use something like the following to only track your themes directory:
/*
/*/
!/wp-content/themes/
I’m marking this as resolved since it has been discussed and it is not required to track the entire repository, only that the parent WordPress installation is installed in one.
Please feel free to post any follow up comments/questions to this thread and I’ll be glad to address them.
Thank you.
Sorry, to clarify on this:
Since Revisr allows you to optionally keep a separate version of each branch…
I meant to say that Revisr allows you to keep a separate version of the files and the database for each branch in Git.
Or you can just track files. Ultimately, it’s however you want to use it and I look forward to seeing new/different implementations.
Thank you for the detailed answer so quickly. I did not realize that Revisr tracks the database as well. That is mighty useful.
Thank you also for developing this great plugin!
