Approvals number on pull request list #3420

New Issue

GiteaMirror · 2025-11-02T05:12:24-06:00

GiteaMirror commented

2025-11-02 05:12:24 -06:00

Originally created by @lunny on GitHub (Jun 3, 2019).

If the approvals number displayed on pull request list, that will help.

Originally created by @lunny on GitHub (Jun 3, 2019). If the approvals number displayed on pull request list, that will help.

GiteaMirror added the issue/confirmed topic/ui type/enhancement labels 2025-11-02 05:12:25 -06:00

GiteaMirror closed this issue

2025-11-02 05:12:25 -06:00

GiteaMirror commented

2025-11-02 05:12:25 -06:00

@stale[bot] commented on GitHub (Aug 2, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Aug 2, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 05:12:26 -06:00

@Toxik1983 commented on GitHub (Feb 14, 2020):

Any indication on when this feature will be implemented? Our team processes a large number of PRs a day, and we use a system of 2 needed approvals. The PRs that have already been approved by one reviewer could more easily be prioritized by the other reviewers if this number was shown in the list.

@Toxik1983 commented on GitHub (Feb 14, 2020): Any indication on when this feature will be implemented? Our team processes a large number of PRs a day, and we use a system of 2 needed approvals. The PRs that have already been approved by one reviewer could more easily be prioritized by the other reviewers if this number was shown in the list.

GiteaMirror commented

2025-11-02 05:12:26 -06:00

@lafriks commented on GitHub (Feb 17, 2020):

I think it's being worked on as should be available in 1.12

@lafriks commented on GitHub (Feb 17, 2020): I think it's being worked on as should be available in 1.12

GiteaMirror commented

2025-11-02 05:12:26 -06:00

@otbutz commented on GitHub (Apr 28, 2020):

https://github.com/go-gitea/gitea/pull/10238

@otbutz commented on GitHub (Apr 28, 2020): https://github.com/go-gitea/gitea/pull/10238

GiteaMirror commented

2025-11-02 05:12:26 -06:00

@zeripath commented on GitHub (Apr 28, 2020):

@otbutz #10238 almost completes this feature but it doesn't give an idea of how many reviews are required - which is why I didn't close this bug with that pr.

@zeripath commented on GitHub (Apr 28, 2020): @otbutz #10238 almost completes this feature but it doesn't give an idea of how many reviews are required - which is why I didn't close this bug with that pr.

GiteaMirror commented

2025-11-02 05:12:26 -06:00

@otbutz commented on GitHub (Apr 28, 2020):

Ah, thanks for that insight. But nevertheless, it's progress ;)

@otbutz commented on GitHub (Apr 28, 2020): Ah, thanks for that insight. But nevertheless, it's progress ;)

GiteaMirror commented

2025-11-02 05:12:27 -06:00

@camlafit commented on GitHub (Jun 10, 2022):

related also to #13594 and #9274
some reverts look be done betweend these PR and actual state

@camlafit commented on GitHub (Jun 10, 2022): related also to #13594 and #9274 some reverts look be done betweend these PR and actual state

GiteaMirror commented

2025-11-02 05:12:27 -06:00

@camlafit commented on GitHub (Jun 10, 2022):

This feature is asked by SPIP community as we have many PR. It'll helpful to process final review/merge with a one page to check state approval :)

@camlafit commented on GitHub (Jun 10, 2022): This feature is asked by SPIP community as we have many PR. It'll helpful to process final review/merge with a one page to check state approval :)

GiteaMirror commented

2025-11-02 05:12:27 -06:00

@brunob commented on GitHub (Jan 29, 2024):

I think this one could be closed now :)

@brunob commented on GitHub (Jan 29, 2024): I think this one could be closed now :)

GiteaMirror commented

2025-11-02 05:12:27 -06:00

@otbutz commented on GitHub (Jan 30, 2024):

@otbutz #10238 almost completes this feature but it doesn't give an idea of how many reviews are required - which is why I didn't close this bug with that pr.

Is that one covered?

@otbutz commented on GitHub (Jan 30, 2024): > @otbutz #10238 almost completes this feature but it doesn't give an idea of how many reviews are required - which is why I didn't close this bug with that pr. Is that one covered?

GiteaMirror commented

2025-11-02 05:12:27 -06:00

@github-actions[bot] commented on GitHub (Feb 29, 2024):

Automatically locked because of our CONTRIBUTING guidelines

@github-actions[bot] commented on GitHub (Feb 29, 2024): Automatically locked because of our [CONTRIBUTING guidelines](https://github.com/go-gitea/gitea/blob/main/CONTRIBUTING.md#issue-locking)

GiteaMirror referenced this issue

2025-11-02 12:22:26 -06:00

[PR #3420] [MERGED] Add mising `LOCAL_WIKI_PATH` documentation #16933

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#3420