* Publish Processing Gradle plugin
Add a publish-gradle job to the release workflow to publish Processing libraries to the Gradle Plugin Portal using gradle publish with required secrets and version/group env vars. Update gradle/plugins/library/build.gradle.kts to use the com.gradle.plugin-publish plugin, provide plugin metadata (website, vcsUrl, displayName, description, tags) and make the plugin id dynamic ("$group.library"). These changes enable automated publishing of the Gradle plugin with the metadata required by the portal.
* Publish plugins in release workflow
* Update build.gradle.kts
* Set project.group system property for tests
Expose the project's group to test JVMs by configuring tasks.withType<Test>() to set systemProperty("project.group", group ?: "org.processing"). Update ProcessingPluginTest to read the plugin id from System.getProperty("project.group") instead of hardcoding the group. Also close the publishing block in build.gradle.kts. This allows tests to adapt when the project group is overridden.
* Update build.gradle.kts
Delete the standalone .github/workflows/pr.yml workflow and comment out the sticky PR comment steps in .github/workflows/build.yml. Artifact upload and build steps remain unchanged; only the actions that post/update pull request comments (marocchino/sticky-pull-request-comment) and associated PR_PAT usage were disabled.
* Add PR artifact uploads and comments
Update the build workflow to handle pull request runs: make the main artifact upload conditional (skip for pull_request), add a separate upload step for PR artifacts with longer retention, and post a sticky PR comment containing a download link. Also adjust workflow permissions to allow pull-request write access and include updated artifact paths.
* Update build workflow: PR comments and artifacts
Add PR-facing comments and artifact wiring to the CI workflow. Post a sticky comment after Gradle tests to indicate artifacts availability, add an upload-artifact step with an id, and update the sticky-comment step to use the artifact output URL (steps.upload-artifact.outputs.artifact-url) and a consistent header. These changes make build artifacts discoverable on pull requests.
* Switch to a table
* update messaging
* Use `processing-bot`
