Closed cfoellmann closed 9 years ago
In order to excercise with Git I imported the assets branch from the original assets folder on the WP.org svn repo, instead of checking out your repo, but the result should be the same.
Since I implemented (build and) deploy to WP.org svn repo with grunt-wp-deploy, which supports natively the WP assets folder, I thinks it's no more really necessary to have a separate branch only for assets on GitHub. What do you think @cfoellmann?
This will improve your workflow. I put the assets in a branch to keep the git repo small (binary files are a killer for Git). You should go with what gives you the best automation
Assets were merged back in main branch in ce9df75fb67cc964347dffd20515ef291f4cd71d
since the screenshots are not doing anything in the plugin in a wp install they should not be included in the download package.
assets
branch and push it into your repo. (Tip: you need to add my repo as an additional remote in your client)