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

Replying to comment to PR in split view fails #3374

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

Originally created by @ptman on GitHub (May 24, 2019).

But it works in unified view

Description

I want to reply to comments in PRs, it only works in unified view, does nothing in split view

Originally created by @ptman on GitHub (May 24, 2019). But it works in unified view - Gitea version (or commit ref): 1.8.1 - Git version: docker - Operating system: docker - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] Yes https://try.gitea.io/basti/gitea/pulls/1/files - [ ] No - [ ] Not relevant - Log gist: ## Description I want to reply to comments in PRs, it only works in unified view, does nothing in split view
GiteaMirror added the type/bug label 2025-11-02 05:10:37 -06:00
GiteaMirror commented 2025-11-02 05:10:38 -06:00
Author
Owner
Copy Link

@lafriks commented on GitHub (May 24, 2019):

I think there was issue already for this

@lafriks commented on GitHub (May 24, 2019): I think there was issue already for this
GiteaMirror commented 2025-11-02 05:10:39 -06:00
Author
Owner
Copy Link

@ptman commented on GitHub (May 24, 2019):

Oh, I'm sorry to open a new one. Could you point me to the existing issue?

@ptman commented on GitHub (May 24, 2019): Oh, I'm sorry to open a new one. Could you point me to the existing issue?
GiteaMirror commented 2025-11-02 05:10:39 -06:00
Author
Owner
Copy Link

@rfwatson commented on GitHub (May 26, 2019):

https://github.com/go-gitea/gitea/issues/4745

@rfwatson commented on GitHub (May 26, 2019): https://github.com/go-gitea/gitea/issues/4745
GiteaMirror commented 2025-11-02 05:10:39 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (May 26, 2019):

duplicated with #4745

@lunny commented on GitHub (May 26, 2019): duplicated with #4745
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 type/bug
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#3374
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?