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.

Add an option to rename branch for "Propose changes" field

See original GitHub issue


When you want to make quick changes to a Repository without having push rights does GitHub offer to “Propose changes” which results in a fork being created and the commit being made to that fork.

However, there is no way for you to define your own branch name when proposing changes and the branch name is always set to a specific pattern.

My feature request is to make Refined GitHub add the radio buttons you usually have for when committing changes to a Repo you have push rights on (The one where you can choose to either commit to the current branch or create a new one from it).


The fact that the branch names are always in the form of :username-patch-:number is kind of frustrating. While it can be a quick and dirty way to propose changes for minor typos, corrections or similar is it still sad that there is no option to actually name your own branch, which often is a crucial part of making pull requests as the branch can give a quick info about what it is. Or perhaps the repository follows a strict naming pattern for branches and deny any patch branch in the process.


Here is a before and after example of how the “Propose changes” field may look like when committing changes for a Repo you don’t have push rights for.

Before: image

After: image

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:1
  • Comments:7 (5 by maintainers)

github_iconTop GitHub Comments

Andre601commented, Sep 17, 2021

No big deal, just let it be patch-1 or just use Codespaces. We can’t add all the features 😅

Or - and that is the option I now chose - make a GitHub feedback:

Andre601commented, Nov 23, 2021

Looks like this was implemented by GitHub?


You misunderstood my issue here… What you’re showing is for when you make changes in a Repo you have write access. My issue is about when you edit a file on a repo you do not have write access… Like go to any repo on the github org and edit a readme there, you’ll see this text box at the bottom: image

Read more comments on GitHub >

github_iconTop Results From Across the Web

Learn How to Rename a Local and Remote Git Branch
Here we'll show you how to use the Git rename branch command step-by-step. ... Using the Git branch command, add an -m option...
Read more >
git - Renaming a branch in GitHub - Stack Overflow
1. Rename your local branch. If you are on the branch you want to rename: git branch -m new-name · 2. Delete the...
Read more >
Renaming a branch - GitHub Docs
Above the list of files, click Branches. ... In the list of branches, to the right of the branch you want to rename,...
Read more >
How to rename and change a Git branch name locally &amp
The steps to change a git branch name are: Rename the Git branch locally with the git branch -m new-branch-name command; Push the...
Read more >
Git Rename Branch – How to Change a Local Branch Name
Step 1: Make sure you are in the root directory for your project · Step 2: Go to the branch you want to...
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 Post

No results found

github_iconTop Related Hashnode Post

No results found