# Which Problems Are Solved

Browse Source

- The git merge commit history is not easily readable
- The single PR commits don't help much in understanding the purpose of a merge commit.
- Often, it requires implicit knowledge to be able to understand what a merge commit is about.

# How the Problems Are Solved

- Ensures that PR descriptions are concise
- Enables configuring GitHub to use the PR descriptions for merge commit messages instead of the PRs single commits
- The ready for review checks are removed from the PR description and instead automatically listed in a PR comment. This comment was created by the action: https://github.com/zitadel/zitadel/pull/7922#issuecomment-2097792384

# Additional Changes
- The acceptance criteria are more concise

# Additional Context

...

This commit is contained in:

Elio Bischof 2024-05-08 09:42:20 +02:00

parent f702192cb1

commit eb551edef3

No known key found for this signature in database

GPG Key ID: 7B383FDE4DDBF1BD

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Show Stats Download Patch File Download Diff File Expand all files Collapse all files

Diff Content Not Available