# Fix issues with drafting release notes in CI \(\#10955\) · gitcafe/zed

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

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

Visibility: public

Requested revision: 583a662ddc06f44dac2b8dc800423a5dab6f8d88

Requested commit: 583a662ddc06f44dac2b8dc800423a5dab6f8d88

Commit: 583a662ddc06f44dac2b8dc800423a5dab6f8d88

Tree: dbed7d60ff643f4f483b6bc7c7ffec581eaf27b8

Author: Marshall Bowers

Committer: GitHub

## Message

```
Fix issues with drafting release notes in CI (#10955)

This PR addresses some issues I ran into with the way we draft release
notes in CI when doing builds.

The first issue I encountered was that `script/draft-release-notes` was
failing, seemingly due to CI doing a shallow Git checkout and not having
all of the tags available in order to compare then. This was addressed
by setting the `fetch-depth` during the Git checkout.

The second issue is that (in my opinion) we shouldn't fail the build if
drafting release notes fails. After well, we're doing it as a
convenience to ourselves, and it isn't a mandatory part of the build.
This was addressed by making any failures in
`script/draft-release-notes` not fail the CI step as a whole.

These changes were already applied to the `v0.133.x` branch.

Release Notes:

- N/A
```

## Parents

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

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