# ci: Ensure assignees can be set for generated PRs \(\#62418\) · gitcafe/zed

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

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

Visibility: public

Requested revision: 4e8057d74db3570b3bd419ff296eb84c35b3a5a3

Requested commit: 4e8057d74db3570b3bd419ff296eb84c35b3a5a3

Commit: 4e8057d74db3570b3bd419ff296eb84c35b3a5a3

Tree: 56b53e9f2195b8b459677abe50fab4b853cf763c

Author: Finn Evers

Committer: GitHub

## Message

```
ci: Ensure assignees can be set for generated PRs (#62418)

Now, this is one of these beautiful cases where GitHubs API ist just so
pleasant to work with: Because PRs are treated as issues, assigning an
assignee to a PR suddenly requires issue write permissions, despite the
issue in question being a PR. Not having that permission resulted in
some missing assignees on zed zippy bumps and failures of the workflows
as seen in
https://github.com/zed-industries/zed/actions/runs/31339736929/job/93311493258.

In comparison, labelling PRs requires PR write permissions as seen in
https://github.com/zed-industries/zed/pull/61525 🤡

Beautiful API and a pleasure to work with, 10/10 would recommend. 

Release Notes:

- N/A
```

## Parents

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

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