Skip to content

Pull upstream/master into fork #2488

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

Closed
1 of 7 tasks
carmenbianca opened this issue Sep 11, 2017 · 6 comments
Closed
1 of 7 tasks

Pull upstream/master into fork #2488

carmenbianca opened this issue Sep 11, 2017 · 6 comments
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/feature Completely new functionality. Can only be merged if feature freeze is not active.

Comments

@carmenbianca
Copy link

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

There is currently no way to pull changes made in upstream into your fork. As a timeline:

  • Fork third-party/project into you/project.

  • third-party/project:master receives new commits.

  • You want to update you/project:master to also contain those commits.

Ideally there would be a very simple button somewhere to achieve this. GitHub and GitLab currently solve this by creating a pull request against yourself, but that is rather clunky and fault-prone (you have to manually make sure to fast-forward). In Gitea I haven't yet found a way to create a pull request against yourself from the upstream repository, but even so it'd be nice just to have a simple button to achieve this task without a pull request.

@lunny lunny added the type/feature Completely new functionality. Can only be merged if feature freeze is not active. label Sep 12, 2017
@lunny lunny added this to the 1.x.x milestone Sep 12, 2017
@stale
Copy link

stale bot commented Feb 12, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale stale bot added the issue/stale label Feb 12, 2019
@lunny lunny added issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented and removed issue/stale labels Feb 13, 2019
@moeenio
Copy link

moeenio commented May 22, 2020

I'd really like to have this; Even if it's creating a pull request like on github/lab.

@gfwing
Copy link

gfwing commented May 22, 2020

I found similar feature in 1.12.0-rc1 when I try the 1.12.0-rc1 yesterday.
圖片

seems: #11327

@moeenio
Copy link

moeenio commented May 23, 2020

Also, I had tried to manually put forkuser:branch in the compare url, but that didn't work. :/ (on stable tho, or maybe i did smth wrong)

@zeripath
Copy link
Contributor

@locness3 The compare page fork options have been substantially improved on 1.12 - so that problem should disappear very soon.

@6543
Copy link
Member

6543 commented Sep 7, 2020

It's posible

@6543 6543 closed this as completed Sep 7, 2020
@lunny lunny removed this from the 1.x.x milestone Sep 8, 2020
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/feature Completely new functionality. Can only be merged if feature freeze is not active.
Projects
None yet
Development

No branches or pull requests

6 participants