Skip to content

Commit cc5993a

Browse files
committed
fix braking formatting
1 parent 417d0b1 commit cc5993a

File tree

1 file changed

+7
-9
lines changed
  • src/assets/YAML/default/BuildAndDeployment

1 file changed

+7
-9
lines changed

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

+7-9
Original file line numberDiff line numberDiff line change
@@ -158,16 +158,14 @@ Build and Deployment:
158158
measure:
159159
Digitally signing artifacts for all steps during the build and especially
160160
docker images, helps to ensure their integrity and authenticity.
161-
description: |
162-
### GitHub Authentication and Commit Signing
163-
To perform a push to a GitHub repository, you must be authenticated. It's important to note that GitHub does not verify if the authenticated user's email address matches the one in the commit.
164-
To clearly identify the author of a commit for reviewers, commit signing is recommended.
165-
166-
GitHub actions such as [semantic-release-action](https://github.com/cycjimmy/semantic-release-action) do not automatically sign commits and may encounter issues as a result.
167-
168-
To address this, you can refer to a working configuration example in the [workflow folder](https://github.com/devsecopsmaturitymodel/DevSecOps-MaturityModel/blob/master/.github/workflows/main.yml) of DSOMM, which demonstrates how to use semantic release action in conjunction with [planetscale/ghcommit-action](https://github.com/planetscale/ghcommit-action).
169-
For added security, consider using [Fine-grained personal access tokens](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/) provided by your organization for a specific repository. Store the Personal Access Token (PAT) as a secret in your project.
161+
description: |-
162+
To perform a push to a GitHub repository, you must be authenticated. It's important to note that GitHub does not verify if the authenticated user's email address matches the one in the commit.
163+
To clearly identify the author of a commit for reviewers, commit signing is recommended.
164+
165+
GitHub actions such as [semantic-release-action](https://github.com/cycjimmy/semantic-release-action) do not automatically sign commits and may encounter issues as a result.
170166
167+
To address this, you can refer to a working configuration example in the [workflow folder](https://github.com/devsecopsmaturitymodel/DevSecOps-MaturityModel/blob/master/.github/workflows/main.yml) of DSOMM, which demonstrates how to use semantic release action in conjunction with [planetscale/ghcommit-action](https://github.com/planetscale/ghcommit-action).
168+
For added security, consider using [Fine-grained personal access tokens](https://github.blog/2022-10-18-introducing-fine-grained-personal-access-tokens-for-github/) provided by your organization for a specific repository. Store the Personal Access Token (PAT) as a secret in your project.
171169
difficultyOfImplementation:
172170
knowledge: 2
173171
time: 2

0 commit comments

Comments
 (0)