# Require release notes to be present \(\#64238\) · gitcafe/zed

[View on GitCafe](https://git.cafe/gitcafe/zed/commit/93f9fce1152dc6b9e345847753e667e3db6dba5c)

Repository: [gitcafe/zed](https://git.cafe/gitcafe/zed)

Visibility: public

Requested revision: 93f9fce1152dc6b9e345847753e667e3db6dba5c

Requested commit: 93f9fce1152dc6b9e345847753e667e3db6dba5c

Commit: 93f9fce1152dc6b9e345847753e667e3db6dba5c

Tree: f778efe2e0f4b35b44ae442dc5e2097ebe5e5aff

Author: Finn Evers

Committer: GitHub

## Message

```
Require release notes to be present (#64238)

Release notes are the sole information users have about what could
either have improved or have been broken for them. Omitting release
notes is one thing, but not writing any or having empty ones helps
nobody - users get no context on what could cause issues they were
seeing nor do they know about potential improvements, triagers cannot
easily find the PR that could have introduced the bug either.

Thus, this PR now makes it so that danger actually requires one to write
release notes. Empty release notes or the placeholder will no longer be
accepted.

Release Notes:

- N/A
```

## Parents

- [0be555891259d06b1c20f475e3f5654fa4797da7](https://git.cafe/gitcafe/zed/commit/0be555891259d06b1c20f475e3f5654fa4797da7?format=markdown)

[Source at this commit](https://git.cafe/gitcafe/zed/tree/93f9fce1152dc6b9e345847753e667e3db6dba5c?format=markdown)