Mention about content-type

.forgejo/workflows/wordpress-plugin.yml

@@ -87,7 +87,8 @@ jobs:
             | jq -r '.id')
 
            # Pushes he zip file to be shown in the "Releases" tab under this release.
-          curl -X POST "${GITHUB_API_URL}/repos/${GITHUB_REPOSITORY}/releases/${RELEASE_ID}/assets?name=${PLUGIN_NAME}.zip" \
+          curl -X POST "${GITHUB_API_URL}/repos/${GITHUB_REPOSITORY}/releases/${RELEASE_ID}/assets" \
             -H "Authorization: token ${{ secrets.GITEA_TOKEN }}" \
-            -H "Content-Type: application/zip" \
+            -F "name=${PLUGIN_NAME}.zip" \
-            --data-binary "@build/${PLUGIN_NAME}.zip"
+            -F "attachment=@${PLUGIN_NAME}.zip"
+

README.md

@@ -1,3 +1,11 @@
 # workflow-sample-wordpress-plugin
 
 A sample workflow that demonstrates how I prefer to store my Wordpress plugins in a repository, and how to publish them to "releases".
+
+Wordpress code is just some ChatGPT sample I asked it to generate. Tested and
+the zip is dumpable.
+
+Worth noting that the way we upload the Zip may not work for Github. Forgejo
+requires a multipart/form-data content type where-as Github may require binary.
+I'm not 100% sure because I don't use Github much at the moment. If you're
+downloading corrupt zips though, this is probably why.