-
-
Notifications
You must be signed in to change notification settings - Fork 5.9k
Closed
Labels
issue/confirmedIssue has been reviewed and confirmed to be present or accepted to be implementedIssue has been reviewed and confirmed to be present or accepted to be implementedtype/bug
Milestone
Description
-
Gitea version (or commit ref):91775c1
-
Operating system: https://try.gitea.io
-
Can you reproduce the bug at https://try.gitea.io:
- To pick up a draggable item, press the space bar. While dragging, use the arrow keys to move the item. Press space again to drop the item in its new position, or press escape to cancel.
Description
If a pull request is open from a forked repo, it will automatically be apply to the source it's forked.
The issue is that we can only see the branch from the source that we've forked and we are unable to easily change the target to apply the pull request.
The only "hack" we can do is change the username or the organisation targeted inside the URL to be able to get the correct usage.
By default I think we need to be able to do pull request inside the repo we work, even if it's a fork.
...
Metadata
Metadata
Assignees
Labels
issue/confirmedIssue has been reviewed and confirmed to be present or accepted to be implementedIssue has been reviewed and confirmed to be present or accepted to be implementedtype/bug
Type
Projects
Relationships
Development
Select code repository
Activity
lunny commentedon Mar 14, 2019
duplicated with #6225 ?
zeripath commentedon Mar 15, 2019
Hmm, I'm not certain if this is the same.
So when you click on PullRequest from a fork it is assumed that you want to merge into the original repository not the fork.
Now, there's no way of changing the base repository easily except to change the URL by hand.
The UI for compare needs to allow you to select the fork repository branches to merge in, and needs to allow you to suggest other repositories. Similarly we need to allow users to change repository for the pulled branch.
salco commentedon Mar 15, 2019
Exact and I think it's best if the "default" PullRequest suggested need to be the repository where the PullRequest is created.
stale commentedon May 15, 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 commentedon May 29, 2019
This issue has been automatically closed because of inactivity. You can re-open it if needed.
wpmp commentedon Aug 2, 2019
Has this issue been resolved?
zeripath commentedon Aug 2, 2019
The compare diff page needs to be rewritten to allow for easy changes to the base repo and head repo
stale commentedon Oct 1, 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.
23 remaining items