Looks great! Can you provide more instruction?

[MickeyKay]

Hi there,

First off, this looks amazing and I would love to start using this setup to mix Git and SVN development.

That said, I'm not quite sure how I'm meant to use this repo. Are there special commands I need to run? Are thing automagically mirrored somehow between the Git and SVN folders?

I would love to see more of a tutorial in the README.md file that explains exactly to use this setup. Thanks!

[vjanssens]

+1

[kevindees]

+1 even just a little more instruction. Such as a list of run commands and what they do in a sentence.

[kodeine]

+1

[meglio]

+1
Did anyone try this? How did it work?

+1, looks interesting some quick info on deployment and workflow application would be great.

[bmarwell]

👍 +1
Yes, I'd love to see a small tutorial on how to init the svn repository if you started with git.

[isevcik]

There is a tutorial how i get it to work:

1. make basic structure like in readme:
   • git directory will contains your plugin code
   • create svn directory by checkouting from svn:
     svn co https://plugins.svn.wordpress.org/your-plugin svn
   • create wp-deploy directory by cloning this repo:
     git clone git@github.com:kasparsd/wp-deploy.git
2. now go to directory wp-deploy and create new tag:
   ./tag.sh 1.0.1
   This will create new tag 1.0.1 in svn and commit it to wordpress.org repository, you will be prompted for username and password

Ensure you have installed svn.

[twoelevenjay]

After following these directions, when I enter:

211J-MacBook-Pro:wp-deploy leon.shelhamer$ ./tag.sh 0.0.3

I get:

`/Users/leon.shelhamer/Desktop/cmb2-admin-extension doesn't seem to be a Git repository'

/Users/leon.shelhamer/Desktop/cmb2-admin-extension is not suppose to be a git repo, /Users/leon.shelhamer/Desktop/cmb2-admin-extension/gitis, can you help with this?

[twoelevenjay]

nevermind, typo in directory path, it works great thank you!

[scrobbleme]

+1 Should be within the readme.

[mallardduck]

@MickeyKay and others, I've commented on the current PR and pinged the repo owner. I'm hoping that they will respond there and update me/(us) on the status of things.

If they are no longer maintaining this project then I may take up my own fork that will include these useful directions and the PR waiting for merge. If that does end up the route things go, I may also work on a scrip that will help you init your plugin code. I'm thinking of some sort of an init script that creates your git and svn folders for you.

Heck, @kasparsd does continue maintaining this I may end up submitting a PR for that setup script idea. Sure you only really need to do it once or twice and it doesn't save a whole lot of time, but it might make any setup directions even easier too!

[kasparsd]

Thank you @mallardduck! I'm happy to accept all the contributions and to keep this project going. Let me review the pull request.