[Repository] Adjust Labels for Pull Requests #1906

New Issue

dpschen · 2022-02-20T10:25:17Z

dpschen commented

2022-02-20 10:25:17 +00:00

Currently the labels in Pull Requests seem to be ones that are made for Issues.

E.g.

every Pull Request should have the label "changes requested".
what would a Pull Request be that is labeled as "question"
[...]

I didn't check but might it be that you can only generaly create labels in Gitea and there is no separation between labels for Issues and Pull Requests? If so, maybe we can add some labels that are better fitting for Pull Requests. Maybe adding a prefix (e.g. PR: ).

Currently the labels in Pull Requests seem to be ones that are made for Issues. E.g. - every Pull Request should have the label "changes requested". - what would a Pull Request be that is labeled as "question" - [...] I didn't check but might it be that you can only generaly create labels in Gitea and there is no separation between labels for Issues and Pull Requests? If so, maybe we can add some labels that are better fitting for Pull Requests. Maybe adding a prefix (e.g. `PR: `).

konrad commented

2022-02-20 16:38:48 +00:00

I think Gitea doesn't differentiate between labels of PRs and issues. Under the hood, each PR has an issue linked to it.

dpschen commented

2022-02-20 17:13:37 +00:00

I think Gitea doesn't differentiate between labels of PRs and issues. Under the hood, each PR has an issue linked to it.

Interesting! What do you think of the prefix-idea?

> I think Gitea doesn't differentiate between labels of PRs and issues. Under the hood, each PR has an issue linked to it. Interesting! What do you think of the prefix-idea?

konrad commented

2022-02-20 17:27:28 +00:00

If there's a label thatt would only work for an issue or a PR I think adding a prefix to them would make a lot of sense. For the rest, we might just want to be careful what to apply where so labels like "question" don't end up on PRs.

👍 1

konrad referenced this issue from a commit

2024-02-07 14:00:34 +00:00

chore(deps): update dependency vitest to v0.10.4 (#1906)

Sign in to join this conversation.