Skip to content

Commit 1914f4c

Browse files
committed
feat: enhance signing description
1 parent dadb178 commit 1914f4c

File tree

1 file changed

+2
-1
lines changed
  • src/assets/YAML/default/BuildAndDeployment

1 file changed

+2
-1
lines changed

src/assets/YAML/default/BuildAndDeployment/Build.yaml

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -159,10 +159,11 @@ Build and Deployment:
159159
Digitally signing artifacts for all steps during the build and especially
160160
docker images, helps to ensure their integrity and authenticity.
161161
description: |
162-
## Github
162+
### Github
163163
You need to be authenticated to perform a push to a Github repository. Github doesn't check if the authenticated user and the mail address in the commit corresponds.
164164
To highlight to reviewers who performed a commit, signing is needed.
165165
Be aware that github actions like [semantic-release-action](https://github.com/cycjimmy/semantic-release-action) will not sign commits and will fail. You find an example working configuration to use semantic release action together with [planetscale/ghcommit-action](https://github.com/planetscale/ghcommit-action) in the [workflow folder](https://github.com/devsecopsmaturitymodel/DevSecOps-MaturityModel/blob/master/.github/workflows/main.yml) of DSOMM.
166+
You might want to utilize [Fine-grained personal access tokens](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/) from your organization for a specific repository and put the Personal Access Token (PAT) as secret into the project.
166167
difficultyOfImplementation:
167168
knowledge: 2
168169
time: 2

0 commit comments

Comments
 (0)