github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Allow reviewers to be added when creating a Pull Request, the same way as assignees can be added #6485

New Issue
Closed
opened 2025-11-02 06:57:23 -06:00 by GiteaMirror · 7 comments
GiteaMirror commented 2025-11-02 06:57:23 -06:00
Owner
Copy Link

Originally created by @ashleykleynhans on GitHub (Dec 8, 2020).

Description

The gitea API allows assignee/assignees to be added when creating a Pull Request using the API.
It would be really useful if the API could also allow reviewer/reviewers to be added in the same way.

Screenshots

N/A

Originally created by @ashleykleynhans on GitHub (Dec 8, 2020). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.30.0 - Git version: N/A - Operating system: CentOS <!-- Please include information on whether you built gitea yourself, used one of our downloads or are using some other package --> <!-- Please also tell us how you are running gitea, e.g. if it is being run from docker, a command-line, systemd etc. ---> <!-- If you are using a package or systemd tell us what distribution you are using --> - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes (provide example URL): https://try.gitea.io/api/swagger#/repository/repoCreatePullRequest - [ ] No - Log gist: <!-- It really is important to provide pertinent logs --> <!-- Please read https://docs.gitea.io/en-us/logging-configuration/#debugging-problems --> <!-- In addition, if your problem relates to git commands set `RUN_MODE=dev` at the top of app.ini --> ## Description The gitea API allows assignee/assignees to be added when creating a Pull Request using the API. It would be really useful if the API could also allow reviewer/reviewers to be added in the same way. ## Screenshots N/A <!-- **If this issue involves the Web Interface, please include a screenshot** -->
GiteaMirror added the type/proposalmodifies/api labels 2025-11-02 06:57:23 -06:00
GiteaMirror commented 2025-11-02 06:57:25 -06:00
Author
Owner
Copy Link

@jpraet commented on GitHub (Dec 23, 2020):

This is currently not possible through the UI either at pull request creation time.
The reviewers can only be added after the PR has been created:

image

@jpraet commented on GitHub (Dec 23, 2020): This is currently not possible through the UI either at pull request creation time. The reviewers can only be added after the PR has been created: ![image](https://user-images.githubusercontent.com/2212615/103026583-912ac200-4554-11eb-91a6-494b3268589b.png)
GiteaMirror commented 2025-11-02 06:57:25 -06:00
Author
Owner
Copy Link

@Sodj commented on GitHub (Feb 16, 2023):

This would be useful

@Sodj commented on GitHub (Feb 16, 2023): This would be useful
GiteaMirror commented 2025-11-02 06:57:25 -06:00
Author
Owner
Copy Link

@muhtarmamatov commented on GitHub (Dec 8, 2023):

Is there any progress on this issue

@muhtarmamatov commented on GitHub (Dec 8, 2023): Is there any progress on this issue
GiteaMirror commented 2025-11-02 06:57:25 -06:00
Author
Owner
Copy Link

@delvh commented on GitHub (Dec 8, 2023):

Technically yes, have a look at CODEOWNERS which ships with 1.21.

@delvh commented on GitHub (Dec 8, 2023): Technically yes, have a look at CODEOWNERS which ships with 1.21.
GiteaMirror commented 2025-11-02 06:57:25 -06:00
Author
Owner
Copy Link

@muhtarmamatov commented on GitHub (Dec 14, 2023):

Thank you @delvh,
Already tested your suggestion if configure with regex reviewers successfully assigned. Problem when assign reviwers to specific folder.

Below example I have tried:

     /docs/  @org-1/Team2
     /frontend/src/   @org-1/Team1
    /folder/sub-folder/  @user1

 
 All three folders(docs, frontend, folder) are located at the root of repository.

@muhtarmamatov commented on GitHub (Dec 14, 2023): Thank you @delvh, Already tested your suggestion if configure with regex reviewers successfully assigned. Problem when assign reviwers to specific folder. > Below example I have tried: ``` /docs/ @org-1/Team2 /frontend/src/ @org-1/Team1   /folder/sub-folder/ @user1 ```    All three folders(docs, frontend, folder) are located at the root of repository.
GiteaMirror commented 2025-11-02 06:57:25 -06:00
Author
Owner
Copy Link

@jpraet commented on GitHub (Dec 29, 2023):

CODEOWNERS seems related, but not exactly what was requested in this issue.

But there is a PR that resolves the requested feature: #26596

@jpraet commented on GitHub (Dec 29, 2023): CODEOWNERS seems related, but not exactly what was requested in this issue. But there is a PR that resolves the requested feature: #26596
GiteaMirror commented 2025-11-02 06:57:25 -06:00
Author
Owner
Copy Link

@jpraet commented on GitHub (Feb 27, 2025):

This has been addressed by #32403.

@jpraet commented on GitHub (Feb 27, 2025): This has been addressed by #32403.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label modifies/api type/proposal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#6485
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?