Improvement of rcommended action for "check-commit-message" run

[christianbe9]

Description

If multiple commits are already available and one commit does not follow the glint rules, then an old commit mit be required to be edited, such that git commit --amend does not work anymore.

Therefore please add:

• branch refs/pull/3055/head -> FETCH_HEAD
  Commit bfaf83f:
  1: T1 Title exceeds max length (78>72): "DR-009-ACL-Concept: Added json scheme and reformatted json example to readable"
  2: B4 Second line is not empty: "json"

Commit 8ca8fc5:
2: B4 Second line is not empty: "SOME/IP and IPC (and preparation for further use cases)"

WARNING: Your commit message does not follow the required format.
Formatting rules: https://eclipse-score.github.io/score/main/contribute/general/git.html
To fix your commit message, run:

git commit --amend
Then update your commit (fix gitlint warnings). Finally, force-push:
git push --force-with-lease

If the non compliant commit is not at HEAD use: git rebase i (e.g. bfaf83f)

Then for the affected commit rename pick to reword

Then save and enter.

Then the commit will be opened -> rework the commit

Then save and enter.

Then force push: git push --force-with-lease

Analysis results

No response

Solution

No response

Error Occurrence Rate

None

How to reproduce

No response

Supporting Information

No response

Classification

Minor

First Affected Release

not released (main)

Last Affected Release

not released (main)

Expected Fixed Release

before release (main)

Category

• Safety Relevant
• Security Relevant

[anmittag]

@christianbe9 which team, are, feature you are assigning the bug?