Build the QQQ IntelliJ resource plugin through the centrally maintained qqq-orb worker. The repository contains only an immutable worker caller; Gradle checks, packaging, diagnostics, and guarded manual signing/publication live in the shared worker.
Validation: the shared worker passed four contract tests and actionlint. This PR provides the first hosted consumer build. The build uses the existing Gradle 8.6 wrapper and Java 17. No Marketplace publication is triggered by this PR; publishing requires an explicit matching version/tag and existing signing credentials. Credential availability and protected-environment configuration still need verification before release activation.
Build the QQQ IntelliJ resource plugin through the centrally maintained qqq-orb worker. The repository contains only an immutable worker caller; Gradle checks, packaging, diagnostics, and guarded manual signing/publication live in the shared worker.
Validation: the shared worker passed four contract tests and actionlint. This PR provides the first hosted consumer build. The build uses the existing Gradle 8.6 wrapper and Java 17. No Marketplace publication is triggered by this PR; publishing requires an explicit matching version/tag and existing signing credentials. Credential availability and protected-environment configuration still need verification before release activation.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Build the QQQ IntelliJ resource plugin through the centrally maintained qqq-orb worker. The repository contains only an immutable worker caller; Gradle checks, packaging, diagnostics, and guarded manual signing/publication live in the shared worker.
Validation: the shared worker passed four contract tests and actionlint. This PR provides the first hosted consumer build. The build uses the existing Gradle 8.6 wrapper and Java 17. No Marketplace publication is triggered by this PR; publishing requires an explicit matching version/tag and existing signing credentials. Credential availability and protected-environment configuration still need verification before release activation.