-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Description
Description
Hello! I love refined Github. I have been yearning for a feature that would make make Github much more useful to me: to always have branch names for PRs shown.
I noticed an issue suggesting this already exists (#190) and is closed, because the feature was implemented in #1641.
For a second I thought maybe I had it disabled, but after looking through the settings and reading the thread in the PR, I realized this functionality was actually removed before the PR was merged: #1641 (comment).
I'm happy to have a jab at implementing this, but am wondering— it sounds like a configuration on an existing feature. Should I add it as a new feature? Is there a way to make existing features configurable?
Motivation
This would be useful to me on two fronts. I imagine people with similar workflows might find it useful for similar reasons too.
- This feature would help me find my own PRs. I'm often working on several branches, all of which have associated PRs. My workflow has me working on several PRs a week, so it's hard to keep track of the "PR Name" <=> "branch name" map.
- This would be very useful to quickly checkout PRs by other contributors/co-workers. I imagine the branch names to be copy-able (maybe with a copy button next to them, or just by virtue of being selectable.
- This can help me keep my repo clean. Some people manually delete: seeing which branches are merged in the list-view, without having to open them one-by-one makes the process much quicker. I personally use a script, so this is not always a concern of mine. Nonetheless, if a PR has local changes that weren't pushed before it was merged (say, a rebase to the latest
main), it won't show up ingit branch --mergedand I it won't be automatically deleted for me. I'd find this feature useful in those cases.
Resolution
As previously mentioned, I can have a jab at this. Thought I'd open a discussion before attempting to implement it to get a general sense of direction pertaining the questions above Should I add it as a new feature? Is there a way to make existing features configurable?
Screenshot
Using the screenshot in #1641 as a starting point, I'd imagine it looking something like this:
