docs: update

Signed-off-by: Carlos Alexandro Becker <caarlos0@users.noreply.github.com>

www/docs/customization/changelog.md

@@ -41,7 +41,6 @@ changelog:
 
   # Paths to filter the commits for.
   # Only works when `use: git`, otherwise ignored.
-  # Only on GoReleaser Pro.
   #
   # Default: monorepo.dir value, or empty if no monorepo
   # Since: v1.12 (pro)

www/docs/customization/nfpm.md

@@ -124,8 +124,6 @@ nfpms:
     # Makes a meta package - an empty package that contains only supporting
     # files and dependencies.
     # When set to `true`, the `builds` option is ignored.
-    #
-    # Default: false
     meta: true
 
     # Changelog YAML file, see: https://github.com/goreleaser/chglog

www/docs/customization/release.md

@@ -27,8 +27,6 @@ release:
 
   # If set to true, will not auto-publish the release.
   # Available only for GitHub and Gitea.
-  #
-  # Default: false
   draft: true
 
   # Whether to remove existing draft releases with the same name before creating
@@ -36,7 +34,6 @@ release:
   # Only effective if `draft` is set to true.
   # Available only for GitHub.
   #
-  # Default: false
   # Since: v1.11
   replace_existing_draft: true
 

www/docs/includes/repository.md

@@ -32,10 +32,16 @@
 
         # Whether to open the PR as a draft or not.
         #
-        # Default: false
         # Since: v1.19
         draft: true
 
+        # If the pull request template has checkboxes, enabling this will
+        # check all of them.
+        #
+        # Since: v1.20 (pro).
+        # This feature is only available in GoReleaser Pro.
+        check_boxex: true
+
         # Base can also be another repository, in which case the owner and name
         # above will be used as HEAD, allowing cross-repository pull requests.
         #

www/docs/scm/gitlab.md

@@ -17,10 +17,12 @@ env_files:
 ```
 
 !!! warning
+
     If you use a project access token, make sure to set `use_package_registry`
     to `true` as well, otherwise it might not work.
 
 !!! warning
+
     If you are using a [protected variable](https://docs.gitlab.com/ee/ci/variables/#protected-cicd-variables)
     to store any of the values needed by goreleaser, ensure that you are protecting the tags as CI jobs in
     Gitlab only may access protected variables if the job is run for protected refs
@@ -49,7 +51,6 @@ gitlab_urls:
 
   # Set this if you set GITLAB_TOKEN to the value of CI_JOB_TOKEN.
   #
-  # Default: false
   # Since: v1.11
   use_job_token: true
 ```
@@ -57,6 +58,7 @@ gitlab_urls:
 If none are set, they default to GitLab's public URLs.
 
 !!! note
+
     Releasing to a private-hosted GitLab CE will only work for version `v12.9+`, due to dependencies
     on [release](https://docs.gitlab.com/ee/user/project/releases/index.html) functionality
     and [direct asset linking](https://docs.gitlab.com/ee/user/project/releases/index.html#permanent-links-to-release-assets).
@@ -65,9 +67,11 @@ If none are set, they default to GitLab's public URLs.
 
 GitLab introduced the [Generic Package Registry](https://docs.gitlab.com/ee/user/packages/package_registry/index.html) in Gitlab 13.5.
 
-Normally, `goreleaser` uploads release files as "attachments", which may have [administrative limits](https://docs.gitlab.com/ee/user/admin_area/settings/account_and_limit_settings.html).  Notably, hosted gitlab.com instances have a 10MB attachment limit, which cannot be changed.
+Normally, `goreleaser` uploads release files as "attachments", which may have [administrative limits](https://docs.gitlab.com/ee/user/admin_area/settings/account_and_limit_settings.html).
+Notably, hosted GitLab instances have a 10MB attachment limit, which cannot be changed.
 
-Uploading to the Generic Package Registry does not have this restriction.  To use it instead, set `use_package_registry` to `true`.
+Uploading to the Generic Package Registry does not have this restriction.
+To use it instead, set `use_package_registry` to `true`.
 
 ```yaml
 # .goreleaser.yml

www/docs/static/schema-pro.json

@@ -2606,6 +2606,9 @@
 					},
 					"draft": {
 						"type": "boolean"
+					},
+					"check_boxes": {
+						"type": "boolean"
 					}
 				},
 				"additionalProperties": false,