Using subcommander as visual client of subversion

Once your plugin has been validated by the wordpress team, you’ll receive an email including your plugin’s address on their svn server:

After you have downloaded and installed subcommander, I suggest you prepare one folder for svn, and one subfolder for each plugin:

In another folder, put all your plugin’s files and tidy it up to save only the files necessary to your plugin’s functioning.

Then start subcommander and create a new project, which you may name as the plugin:

About the working copy, I personnally leave it blank at this stage.

It then asks for your trunk folder’s urls (see wordpress’ email):

For the other folders, use the standard layout:

This finishes the project’s creation. At this point, subcommander shows three distant folders: trunk, tags and branches, still empty on the server:

then comes the first checkout:

Precising local and distant folders, at their root:

Once checkout is finished, Subcommander will have synchronised your working copy with the server. In other words, it’ll have recreated the identical folder structure:

Then copy with windows’ explorer your plugin files into the working copy’s trunk folder:

Go back to subcommander and, after having checked “all”, you’ll see the working copy’s folders:

to see the folders’ content, you need to select working copy’s trunk for example, and activate the refresh and reload icons (under the menu bar):

Then select each plugin’s folder and file, and add them using the additem menu:

At the end, every file will have gone from “?” status to “A”, standing for added.

The next step consists in transmitting files to the server. We’ll do this with a commit of the working copy’s trunk folder:

You need to write a message for each commit, to indicate what’s new:

During the first commit, subcommander will ask for your login, which is identical to the one you use on wordpress.org.

To check that the commit was successful, have a look on the server:

You can also refresh the distant trunk folder in subcommander to check that everything went well.

Eventually you need to wait 15 minutes until wordpress’ site has updated, and published your plugin:

Spread this post over the world!

How did you like this post?

Please don't go without leaving a mark!
0 vote  Loading ...