If you want some advice you could use TortoiseSVN for Windows and RapidSVN for Linux and Mac.
Posted: Sun Jan 05, 2025 9:15 am
The plugin must be released under GPL2.0 or later
Do not post offensive or illegal material, even if you are unlikely to do so, it is always better to remember this.
Do not insert links in the code in the hope of getting backlinks without the explicit consent of the user or without giving him the possibility to easily remove it. In case you want to choose to put it by default and give the user the possibility to remove it, SPECIFY IT WELL both in the documentation and in the readme
The rest, as WordPress.org also tells us, is just a series of rules that explain how not to be a portugal phone number data spammer.
Once you receive confirmation of the plugin review, you will be provided with the link to your repository and the credentials to access it. At this point, look for a GUI for SVN to make the operations faster and more practical. Since we are talking about writing folder paths and URLs, we will leave the command line to the more daring, who we will refer to reading the Codex .
Now it's time to introduce some general concepts of the subversioning system to help you master the code review and publishing operations. The main operations you will do will be 3:
Import the repository (this is usually done the first time and if you want to work on multiple workstations)
Add files to the commit list
Make the Commit
Let's start with order, take the SVN client you have chosen and import ( checkoutthis is the term you will find in many cases) the repository structure in a folder specifically created by (I put it in the folder /home/progetti/glossary-by-codeat/), using the link and credentials provided by WordPress.
At this point you will notice that some subfolders have been automatically created in the folder, let's examine them carefully.
/trunk/
Here we will put the code we are currently working on, it can easily be the latest stable one if you are not planning anything new, the important thing is that this is the first folder filled with all the files and folders used by the plugin , including our dear readme.txt.
Do not post offensive or illegal material, even if you are unlikely to do so, it is always better to remember this.
Do not insert links in the code in the hope of getting backlinks without the explicit consent of the user or without giving him the possibility to easily remove it. In case you want to choose to put it by default and give the user the possibility to remove it, SPECIFY IT WELL both in the documentation and in the readme
The rest, as WordPress.org also tells us, is just a series of rules that explain how not to be a portugal phone number data spammer.
Once you receive confirmation of the plugin review, you will be provided with the link to your repository and the credentials to access it. At this point, look for a GUI for SVN to make the operations faster and more practical. Since we are talking about writing folder paths and URLs, we will leave the command line to the more daring, who we will refer to reading the Codex .
Now it's time to introduce some general concepts of the subversioning system to help you master the code review and publishing operations. The main operations you will do will be 3:
Import the repository (this is usually done the first time and if you want to work on multiple workstations)
Add files to the commit list
Make the Commit
Let's start with order, take the SVN client you have chosen and import ( checkoutthis is the term you will find in many cases) the repository structure in a folder specifically created by (I put it in the folder /home/progetti/glossary-by-codeat/), using the link and credentials provided by WordPress.
At this point you will notice that some subfolders have been automatically created in the folder, let's examine them carefully.
/trunk/
Here we will put the code we are currently working on, it can easily be the latest stable one if you are not planning anything new, the important thing is that this is the first folder filled with all the files and folders used by the plugin , including our dear readme.txt.