-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add steps to example workflow around ZIP generation #4
Labels
Milestone
Comments
helen
added
type:enhancement
New feature or request.
needs:documentation
This requires documentation.
labels
Aug 31, 2019
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Is your enhancement related to a problem? Please describe.
With the new
.distignore
method of excluding files from deployment, the GitHub-generated ZIP file attached to releases no longer reflects what gets deployed to .org. Also, broadly that automatic naming is an issue, as you'll getplugin-slug-X.Y.Z
as the folder name upon unzipping, which is not really what you or WordPress want.Describe the solution you'd like
Test additional steps in a test repo workflow and then add them to
README.md
. My sense is that existing Actions can be leveraged to generate the ZIP and attach it to a release, but don't know yet. If not, we can write one, which will also be useful for plugins that don't release to .org at all and update directly from GH instead.The text was updated successfully, but these errors were encountered: