-
-
Notifications
You must be signed in to change notification settings - Fork 6.2k
Description
- Gitea version (or commit ref): 1.12.0
- Git version:
- Operating system: ubuntu
- Database (use
[x]):- PostgreSQL
- MySQL
- MSSQL
- SQLite
- Can you reproduce the bug at https://try.gitea.io:
- Yes (provide example URL) https://try.gitea.io/my1e5_test/Merge-Pull-Request/pulls/1
- No
- Not relevant
- Log gist:
Description
When merging a pull request, Gitea automatically generates text for the commit message. It has the following format:
TITLE: Merge pull request 'pull-request-name' (#pull-request-number) from branch into branch
CONTENT: Reviewed-on: url-of-pull-request
However, I've noticed a potential bug with the way it constructs the branch names. The first branch name is structured like:
organisation-name/branch-name
when I think it should be
organisation-name/repo-name/branch-name OR just branch-name
See the try.gitea example repo and the screenshots below for examples of this.
Screenshots
Organisation: my1e5_test
Repo: Merge-Pull-Request
Branch: feature/my_branch
I use a folder structure for my branch name. I am merging into master.
Notice how it says "from my1e5_test/feature/my_branch into master".
In my opinion this is not accurate. It should be just "from feature/my_branch into master" OR it should be "from my1e5_test/Merge-Pull-Request/feature/my_branch into master".
Missing out the repo name, but having the organisation name, is strange IMO.
