This keeps the filesizes of plugins small, as it is not necessary to send screenshots to WordPress installations along with the plugin itself. All new plugins should put their screenshots in /assets. Some older plugins in the directory may have screenshot files in /trunk instead, however this is not recommended. Note: See also: How Your Plugin Assets WorkĪssets is where your screenshots, header images, and plugin icons reside.
#SMARTSVN ROLLBACK TO REVISION LOCALLY SOFTWARE#
We strongly encourage the use of semantic software versioning. Version 1.0 of the plugin will be in /tags/1.0, version 1.1 would be in /tags/1.1, and so forth. It is important that you always use tag folders and proper versioning to ensure your users get the correct code. You will use the same version numbers for the sub-directories here as you do for your plugin versioning. The /tags directory is where you put versions of the plugin.
#SMARTSVN ROLLBACK TO REVISION LOCALLY CODE#
For simple plugins, the trunk may be the only version of the code that exists, and that’s fine as well.Įven if you do your development work elsewhere (like a git repository), we recommend you keep the trunk folder up to date with your code for easy SVN compares. Hopefully, the code in trunk should always be working code, but it may be buggy from time to time because it’s not necessarily the “stable” version.
The trunk can be considered to be the latest and greatest code, however this is not necessarily the latest stable code. The /trunk directory is where your plugin code should live. You may use subfolders for included files. Warning: Do not put your main plugin file in a subfolder of trunk, like /trunk/my-plugin/my-plugin.php as that will break downloads. There are three directories created by default in all SVN repositories. If you need to reset your password, go to You can see the specific capitalization of your name at Remember, capitalization matters - if your username is JaneDoe, then you must use the capital J and D or else SVN will fail. This is the user ID you use for the WordPress forums as well. Your account for SVN will be the same username (not the email) of the account you used when you submitted the plugin. Tags are great for labeling different releases of your plugin and are the only fully supported method of ensuring the correct versions are seen on and updated for users. In addition to remembering each individual revision, you can tell subversion to tag certain revisions of the repository for easy reference. Subversion keeps track of all these changes so that you can go back and look at old versions or revisions later if you ever need to. It’s this process of checking in that updates both the files in the repository and also the information displayed in the Plugin Directory. That means you can make changes to the files, add new files, and delete files on your local machine and upload those changes back to the central server. From that repository, anyone can check out a copy of your plugin files onto their local machine, but, as a plugin author, only you have the authority to check in. Overview # OverviewĪll your files will be centrally stored in the svn repository on our servers. Please only push finished changes to your SVN repository. Unlike Git, you shouldn’t commit every small change, as doing so can degrade performance. Warning: SVN and the Plugin Directory are a release repository.
If you’re new to SVN, we recommend reviewing a comparison of SVN clients before deciding which is best for you. It can be used via command line, or one of numerous GUI applications, such as Tortoise SVN, SmartSVN, and more. SVN, or Subversion, is a version control system similar to Git.
0 kommentar(er)
