[UI] Pull request page doesn't contain repo name #853

New Issue

GiteaMirror · 2025-11-02T03:39:05-06:00

GiteaMirror commented

2025-11-02 03:39:05 -06:00

Originally created by @schmittlauch on GitHub (Jun 28, 2017).

Gitea version (or commit ref): 1.1.2
Git version: 2.12.3
Operating system: openSUSE (Linux)
Database (use [x]):
- PostgreSQL
- MySQL
- MSSQL
- SQLite
Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL)
- No
- Not relevant

Description

The text about which branch should be merged into which other branch doesn't contain the name of the repository. In the screenshot below, it has the form organisation/branch
In my opinion the current behaviour is not really intuitive, it should either have the form org or user/repo:branch or just repo:branch.

Screenshots

Originally created by @schmittlauch on GitHub (Jun 28, 2017). - Gitea version (or commit ref): 1.1.2 - Git version: 2.12.3 - Operating system: openSUSE (Linux) - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant ## Description The text about which branch should be merged into which other branch doesn't contain the name of the repository. In the screenshot below, it has the form `organisation/branch` In my opinion the current behaviour is not really intuitive, it should either have the form `org or user/repo:branch` or just `repo:branch`. ## Screenshots ![screenshot_20170628_114846](https://user-images.githubusercontent.com/1479555/27635580-df3df5e6-5c07-11e7-8ca7-847f061951d2.png)

GiteaMirror added the type/enhancement label 2025-11-02 03:39:05 -06:00

GiteaMirror closed this issue

2025-11-02 03:39:05 -06:00

GiteaMirror commented

2025-11-02 03:39:06 -06:00

@bkcsoft commented on GitHub (Jun 28, 2017):

if it's changed go for owner/repo:branch. Since if you go for repo:branch you don't know which fork it's coming from :)

@bkcsoft commented on GitHub (Jun 28, 2017): if it's changed go for `owner/repo:branch`. Since if you go for `repo:branch` you don't know which fork it's coming from :)

GiteaMirror commented

2025-11-02 03:39:06 -06:00

@lafriks commented on GitHub (Jun 28, 2017):

I think best would be something like that: ... from fork_owner/repo:branch into devel

@lafriks commented on GitHub (Jun 28, 2017): I think best would be something like that: `... from fork_owner/repo:branch into devel`

GiteaMirror referenced this issue

2025-11-02 11:50:37 -06:00

[PR #853] [MERGED] Consistency checks for unit tests #15612

GiteaMirror referenced this issue

2025-11-02 11:50:45 -06:00

[PR #859] [MERGED] Fix broken test fixture #15617

Sign in to join this conversation.