Conversation
|
For me that sentence makes sense but is unclear. The message is that a proper zip file, regardless of the name of the ZIP file, expands to a folder that is named as the plugin/theme slug. |
|
Do you mean in this example "doit-" is always added automatically? Or do you mean the folder name "doit" in the path? |
|
I mean that you can have even a ZIP named That said, the action creates a "properly crafted zip file" means what I said before. |
|
Totally forgot, we talked about this before! That info is for people that host their software outside GH, but need a properly crafted zip file for the CP Directory, right? If I'm right, I will undo my previous commit. Agree? |
|
Even "You can also add a ZIP file (that contains your plugin or theme) from elsewhere, as long as it has the same name format as explained below." is not related to the workflow. The workflow is intended to create a proper ZIP for you, maybe that infos belongs to directory instructions. |
|
Good point, the Directory Requirements docs already contain some release info (See Releases heading). It does not contain the info about the included folder name. We can decide to remove the info from this repo and include it in the docs instead? |
|
I think that it's the best solution. |
As discussed with Simone
|
Do you agree with my latest commit? I will update the docs later. |
Minor change: the last part of the sentence makes no sense.