Skip to content

Pull request Reference #13134

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
7 tasks
zhoutt96 opened this issue Oct 13, 2020 · 1 comment
Open
7 tasks

Pull request Reference #13134

zhoutt96 opened this issue Oct 13, 2020 · 1 comment
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@zhoutt96
Copy link

  • Gitea version (or commit ref):
  • Git version:
  • Operating system:
  • 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

In bitbucket: they have two refs for each pull request, shown as below.
0cac01dd5ba4741a14cfb7d28bc4873aefebc4eb refs/pull-requests/#/from
4d19d85730dc74d23c3d92fa7392a1e389d017f4 refs/pull-requests/#/merge

In your project, only found refs/pull/#/head which points to lastest commit of head branch, how about the refs/pull-requests/#/merge refs?
...

Screenshots

@zeripath
Copy link
Contributor

zeripath commented Oct 13, 2020

We don't currently have this - but the merge commit id is stored in the pull_request table.

@lunny lunny added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Apr 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

No branches or pull requests

3 participants