Skip to content

Commit fc7d915

Browse files
committed
Add item about how to publish plugin
1 parent f4d61cd commit fc7d915

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

DEVELOPMENT_GUIDE.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,9 @@ In the [.github/workflows/](.github/workflows/) folder you can find scripts for
5050

5151
* The most important one is the [`checks.yaml`](.github/workflows/checks.yaml): it installs the necessary dependencies, runs the linters and implemented tests, and, finally, executes several checks to make sure the plugin actually provides the tasks in the example project.
5252
* The [`gradle-wrapper-validation.yaml`](.github/workflows/gradle-wrapper-validation.yml) also runs on each pull-request: it simply checks that the gradle wrapper has a valid checksum.
53-
* The [`publish-plugin.yaml`](.github/workflows/publish-plugin.yaml) one automatically publishes the plugin whenever new tag is pushed. It requires some environment set-up, check the publish plugin section for the details (TODO).
53+
* The [`publish-plugin.yaml`](.github/workflows/publish-plugin.yaml) one automatically publishes the plugin whenever new tag is pushed.
54+
* It requires some environment set-up to finish successfully. Namely, two GitHub secrets should be set: `GRADLE_PUBLISH_KEY` and `GRADLE_PUBLISH_SECRET` with the credentials that can be found in the Gradle Portal profile. However, it should be done only once for the repo.
55+
* Moreover, before publishing the plugin don't forget to get acquainted with the Gradle Portal publishing rules. There exist many limitations on plugin's metainformation and project's appearance.
5456

5557
## Future plans
5658

0 commit comments

Comments
 (0)