Use SVN copy from trunk to new tag folder to improve deploy times about action-wordpress-plugin-deploy HOT 3 CLOSED

@jeffpaul I'd be open to helping, you can ping me on Post Status slack (if your there) & would like to discuss it.

Otherwise I can likely work it out and submit a PR if that's all you mean.

from action-wordpress-plugin-deploy.

Hello! Otto actually asked us to do it this way to avoid the second commit and load on .org, not sure if he would still want that today so you could ask, see 10up/actions-wordpress#4 for the history

from action-wordpress-plugin-deploy.

@helen

This prevents that middle moment when the readme in trunk points to a tag that you haven't created yet. Both trunk and the tagged version are sent at the same time.

That makes since.

Despite what some think, this doesn't result in extra data use. Svn knows how to deal with local cp commands.

This seems highly inaccurate, pretty easy test to see that both transmission time & data sent are near doubled when doing this method.

That said the prior reason holds, short of a 3rd svn push to change the readme stable tag separately after tag copy, which makes even less since.

from action-wordpress-plugin-deploy.