Skip to content

Commit 0a03269

Browse files
committed
docs: removes links to repo settings not accessible for non-maintainers
1 parent 0d5089c commit 0a03269

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -91,7 +91,7 @@ The GH actions job [callable.publish-sonatype.yml](.github/workflows/callable.pu
9191
| `GPG_SIGNING_KEY` | The GPG private key to sign your artifacts (in ascii-armored format). You can obtain it with `gpg --armor --export-secret-keys <[email protected]>` or you can create one key online on [pgpkeygen.com](https://pgpkeygen.com). |
9292
| `GPG_SIGNING_PASSPHRASE` | The passphrase for unlocking the secret key. (you picked it when creating the key). |
9393

94-
Please define the secrets via your repository settings. ([Settings > Security > Secrets and variables > Actions](settings/secrets/actions))
94+
Please define the secrets via your repository settings. (Settings > Security > Secrets and variables > Actions)
9595
<img width="800" alt="Preview of Javadoc published to GitHub Pages by the CI/CD pipeline" src="https://github.com/thriving-dev/java-library-template/assets/10864443/e6cf928c-6665-43fc-9506-c29d210b18de">
9696

9797
## Release Process
@@ -144,7 +144,7 @@ To host the generated Javadoc, configure GitHub Pages for your repository to dep
144144

145145
## Security & CodeQL Analysis
146146
### Common Vulnerabilities and Exposures (CVE)
147-
The libraries gradle dependencies are scanned for known [CVE](https://www.cve.org/) with **[aquasecurity/trivy](https://github.com/aquasecurity/trivy)**. The scan results can be reviewed and managed under [Security > Vulnerability alerts > Code scanning](https://github.com/thriving-dev/java-library-template/security/code-scanning).
147+
The libraries gradle dependencies are scanned for known [CVE](https://www.cve.org/) with **[aquasecurity/trivy](https://github.com/aquasecurity/trivy)**. The scan results can be reviewed and managed under 'Security > Vulnerability alerts > Code scanning'.
148148

149149
Scans are triggered
150150
1. with each main CI/CD pipeline run

0 commit comments

Comments
 (0)