There is no general solution to this problem. Your solution will be specific to your situation, and unusable for many other users, and vice versa. All with their own varying tradeoffs. For example, some hosting companies spin up new instances with the new update, that then replace the old instances, but this is not possible … Read more
You can try using Source Tree https://www.sourcetreeapp.com/, no need to learn heavily the command line git, all the non coders need to do is copy their files to your repo, then commit and push if there are no complications that will arise. The only bad side of this is if there will be merge issues … Read more
what’s the best way to go about editing commit messages? Don’t worry about it, don’t make such mistake in future “ask the administrator to create a pre-revprop-change hook”
I have not directly an answer to solve your issue as it (please take a look at the edit part I add), but this codesnippet (function) could maybe help you to solve the version issues for .js as well for .css files. /** * Remove query (output)string from .js / .css * Using filters */ … Read more
It is good practise to use semantic versioning e.g. 1.0.1 MAJOR.MINOR.PATCH MAJOR version when you make incompatible changes, MINOR version when you add functionality in a backwards-compatible manner, and PATCH version when you make backwards-compatible bug fixes. Don’t update the version on every code commit in git (just do it manually), rather on every group … Read more
Perhaps write your custom themes as a child of the base theme, then set up a self-hosted theme update. Whenever you make changes to your base theme, push it to your update server with whichever version control you opt for (SVN, Git etc.), and it’ll become available as a “regular” update to all your sites … Read more
If my guess is right that you think you add your site URL inside the plugin’s head and it will magically update everyones plugin, then I have to tell you that wont work. You have choices: Either you host your plugin on wordpress.org and updates work pretty much without you doing anything then pushing your … Read more
To make changes in live site with local install you need to setup a synchronization system. which synchronize static files and database files. You can use Git for version control. Here is a great article for Sync A Local and A Remote WordPress Blog using version control.
The command you need is patch which is not specific to SVN. It’s really easy to do. See this article: http://jungels.net/articles/diff-patch-ten-minutes.html
Do I still need to include the update scripts in version 1.2 so people can update the plugin from v1.1 directly to v1.3? Yes. Is there a way for WordPress to automatically download v1.2, run the update scripts, and then download v1.3… No. …is there a way to flag v1.3 of my plugin and say, … Read more