You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/assets/YAML/generated/generated.yaml
+5-3Lines changed: 5 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -185,14 +185,16 @@ Build and Deployment:
185
185
or container images.
186
186
measure: Digitally signing artifacts for all steps during the build and especially
187
187
docker images, helps to ensure their integrity and authenticity.
188
-
description: "## Github\nYou need to be authenticated to perform a push to a
189
-
Github repository. Github doesn't check if the authenticated user and the
188
+
description: "### Github\nYou need to be authenticated to perform a push to
189
+
a Github repository. Github doesn't check if the authenticated user and the
190
190
mail address in the commit corresponds. \nTo highlight to reviewers who performed
191
191
a commit, signing is needed.\nBe aware that github actions like [semantic-release-action](https://github.com/cycjimmy/semantic-release-action)
192
192
will not sign commits and will fail. You find an example working configuration
193
193
to use semantic release action together with [planetscale/ghcommit-action](https://github.com/planetscale/ghcommit-action)
194
194
in the [workflow folder](https://github.com/devsecopsmaturitymodel/DevSecOps-MaturityModel/blob/master/.github/workflows/main.yml)
195
-
of DSOMM.\n"
195
+
of DSOMM.\nYou might want to utilize [Fine-grained personal access tokens](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/)
196
+
from your organization for a specific repository and put the Personal Access
0 commit comments