We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Using a workflow to collate the files into a zip, and this action https://github.com/softprops/action-gh-release, it should be possible to create a library.zip file for Processing from the repository (according to the spec at https://github.com/benfry/processing4/wiki/Library-Guidelines#folder-structure).
This would be hosted under a "latest" tag.
Automatic Processing-ready builds with a permalink.
No response
The text was updated successfully, but these errors were encountered:
The template already does this https://github.com/processing/processing-library-template/blob/main/.github/workflows/release.yml When you create a new release, the necessary files, including the .zip will be crated automatically
Sorry, something went wrong.
Oh, ok. There are no releases in this repo so I guessed it wasn't a feature.
Thanks for your input! @mingness Do you think adding an example release to the repo would be helpful?
That's a good idea @Stefterv. Thanks for the feedback @micycle1, and your jitpack repo of processing. We used it until the official release on maven.
No branches or pull requests
Describe the feature or enhancement
Using a workflow to collate the files into a zip, and this action https://github.com/softprops/action-gh-release, it should be possible to create a library.zip file for Processing from the repository (according to the spec at https://github.com/benfry/processing4/wiki/Library-Guidelines#folder-structure).
This would be hosted under a "latest" tag.
What is the use case?
Automatic Processing-ready builds with a permalink.
Alternatives considered
No response
The text was updated successfully, but these errors were encountered: