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

the review comment on a pr is always in pending status #5697

New Issue
Closed
opened 2025-11-02 06:33:26 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 06:33:26 -06:00
Owner
Copy Link

Originally created by @bigwhite on GitHub (Jul 6, 2020).

  • Gitea version (or commit ref): Gitea version 1.12.1 built with GNU Make 4.1, go1.14.4 : bindata, sqlite, sqlite_unlock_notify
  • Git version: git version 2.20.1 (Apple Git-117)
  • Operating system: macos
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

the review comment on a pr is always in pending status. and after update the pr, these comments all disappeard.

bs. the try.gitea.io is accessed too slow . I did not try to reproduce in this site.

Screenshots

image

Originally created by @bigwhite on GitHub (Jul 6, 2020). - Gitea version (or commit ref): Gitea version 1.12.1 built with GNU Make 4.1, go1.14.4 : bindata, sqlite, sqlite_unlock_notify - Git version: git version 2.20.1 (Apple Git-117) - Operating system: macos - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [ ] Not relevant - Log gist: ## Description the review comment on a pr is always in pending status. and after update the pr, these comments all disappeard. bs. the try.gitea.io is accessed too slow . I did not try to reproduce in this site. ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** --> ![image](https://user-images.githubusercontent.com/419088/86584868-242c6b80-bfb8-11ea-9de9-4f1de484cf22.png)
GiteaMirror commented 2025-11-02 06:33:27 -06:00
Author
Owner
Copy Link

@bigwhite commented on GitHub (Jul 6, 2020):

i am sure the database is running ok.

@bigwhite commented on GitHub (Jul 6, 2020): i am sure the database is running ok.
GiteaMirror commented 2025-11-02 06:33:27 -06:00
Author
Owner
Copy Link

@a1012112796 commented on GitHub (Jul 6, 2020):

hello, I think you should submit your review after add comments.

@a1012112796 commented on GitHub (Jul 6, 2020): hello, I think you should submit your review after add comments.
GiteaMirror commented 2025-11-02 06:33:27 -06:00
Author
Owner
Copy Link

@zeripath commented on GitHub (Jul 6, 2020):

This is a common problem - I think this UI is poor (although it essentially replicates GHs behaviour).

@bigwhite you need to click the Review button in the top right and press one of approve, comment, request changes.

@zeripath commented on GitHub (Jul 6, 2020): This is a common problem - I think this UI is poor (although it essentially replicates GHs behaviour). @bigwhite you need to click the Review button in the top right and press one of approve, comment, request changes.
GiteaMirror commented 2025-11-02 06:33:27 -06:00
Author
Owner
Copy Link

@bigwhite commented on GitHub (Jul 6, 2020):

This is a common problem - I think this UI is poor (although it essentially replicates GHs behaviour).

@bigwhite you need to click the Review button in the top right and press one of approve, comment, request changes.

@zeripath got it , it works. thank you

@bigwhite commented on GitHub (Jul 6, 2020): > This is a common problem - I think this UI is poor (although it essentially replicates GHs behaviour). > > @bigwhite you need to click the Review button in the top right and press one of approve, comment, request changes. @zeripath got it , it works. thank you
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
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#5697
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?