question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Option to choose repository where to edit the current file

See original GitHub issue

Currently if I’m editing something on my fork through the edit view and I’ll choose to create a new branch and start a pull request, GitHub will redirect me to “Open a pull request” page on the fork I used, not at the repository I forked. While this makes sense, I think it would be great if I were also able to choose different base repository.

Example URL: https://github.com/jack1142/refined-github/new/master Where jack1142/refined-github is someone’s fork you have write access to.

Draft of what I mean (by no means should it be styled like this, but I’m not a web designer 😛) image


When I was doing some checking, it looks like this would be possible to solve by editing value of hidden input field with name="quick_pull" that is placed in the form I sent a screenshot of above. For example, if the value of it is master, changing it to sindresorhus:master is gonna make it redirect me to “Open a pull request” page for sindresorhus/refined-github repository instead.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:3
  • Comments:13 (13 by maintainers)

github_iconTop GitHub Comments

1reaction
Jackenmencommented, Jul 29, 2020

Maybe this could be cached similarly how showing the link to fork (near the fork button at the top of repository) is cached?

0reactions
Jackenmencommented, Jul 30, 2020

Just edit them on the original repository and GitHub will take you through the correct path of forking, if necessary, and proposing the file on the original repo

But that’s not what I want - I always want to use fork, even if I have the write perm to the original repository. Our workflow is based on forks and we generally avoid creating branches on original repo. I know this project is opinionated, but it seemed valid to ask for a feature that allows to (but doesn’t force you to) choose to which repo you want to make PR, regardless of what repo you’re making the branch on.

Those are valid points, a new issue can be opened for those

I’ll make issue(s) for those in a moment then.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Editing files - GitHub Docs
In another user's repository, browse to the folder that contains the file you want to edit. Click the name of the file you...
Read more >
Add, edit, and commit to source files | Bitbucket Cloud
Edit files online · A. File heading – Displays the repository owner (workspace), the project where it lives, and the repository's name. ·...
Read more >
Check out and edit files - Azure Repos | Microsoft Learn
In Visual Studio Solution Explorer or Source Control Explorer, select the files you want to edit, right-click, and select Check Out for Edit....
Read more >
Creating and Editing Changes in the Gerrit Web Interface
From the Gerrit Code Review dashboard, select Browse > Repositories. · Under Repository Name, click the name of the repository you want to...
Read more >
Edit files through the command line - GitLab Docs
Alternatively, you can edit files using your choice of editor (IDE), or the GitLab user ... ls a*, List what's in the current...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found