Page 1 of 1

Here we are helped by the word itself that tells us

Posted: Sun Jan 05, 2025 9:15 am
by najmus96
This folder must contain subfolders named with the version number , you can start by creating the 1.0 and copying the contents of /trunk/. The way you should proceed is, in fact, to work in the trunk folder and then, once the code is finished and tested, create a new folder in /tags/and copy everything directly into it, being careful to then change the stable version number in the readme both in the trunk and in the current folder .

/branches/
the function of the folder. Obviously if you are publishing it for the first time it is unlikely that you qatar phone number data have branches available, but if you feel the need to use them this is the folder where to place all the code!

/assets/

This folder is basically at your disposal to put everything that could be useful to you, I use it to update the documentation for example. The main function of this folder is to allow us to upload the banner and screenshots of our plugin to be shown on the relative page on wordpress.org.

The screenshots must be renamed in this form <em>screenshot-1.pngwith a progressive number, to be associated with the relative description that we have put in the readme while the banner must be a png of 772×250 pixels and must be called banner-772x250.png.

Fill the various folders with the right files that you will need to add ( addin many clients) and then commit ( commit). Double check that you have added all the files, even those in the subfolders of your plugin, before doing commit. Having an SVN client is handy because it signals changes in the folders and lets us know about any version misalignments with the server.

Let's remember that to "push" an update for the plugin, just change the stable parameter of the readme placed in the /trunk, so first we create the folders, commit everything in the folder relating to the new version and change it in its readme.txtand then also in that of the /trunk!