This is an automated email from the ASF dual-hosted git repository.
jdaugherty pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/grails-gradle-publish.git
The following commit(s) were added to refs/heads/main by this push:
new 5b0cceb doc: formatting cleanup
5b0cceb is described below
commit 5b0cceb26e468e9ffe2b8af03ee8658eb56457d2
Author: James Daugherty <[email protected]>
AuthorDate: Sun Oct 5 10:41:25 2025 -0400
doc: formatting cleanup
---
README.md | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/README.md b/README.md
index 52c89e6..5766495 100644
--- a/README.md
+++ b/README.md
@@ -66,8 +66,10 @@ And then apply the plugin:
apply plugin: 'org.apache.grails.gradle.grails-publish'
```
-Plugin Configuration: Initial Setup
+Plugin Configuration
---
+
+### Initial Setup
Example Configuration:
grailsPublish {
@@ -120,7 +122,7 @@ The credentials and connection url must be specified as a
project property or an
By default, a `release` or `snapshot` build is determined by the
`project.version` or `projectVersion` gradle property. To override this
behavior, use the environment variable `GRAILS_PUBLISH_RELEASE` with a boolean
value to indicate if the build is a `release` or `snapshot`.
-### Plugin Configuration: Release Signing
+### Release Signing
`release` builds are expected to be signed by this build. To disable this
behavior, add the following Gradle code:
