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.

Branch list-related features request

See original GitHub issue

Request 1: Option to do not divide the branches list into “Recent” and “Other” branches - since the “recent” branch is not necessarily the branch you have been working on recently. I can select and view all my branches one-by-one and the previous of recent branch will be shown as “Other”. Note that I did not do any changes to the branches.

Request2: Option not to change the position of the branch in the list after I selected it. When I choose a branch it is lifted up to the first place under the “Recent branches” list. This prevents me from going through the full list of branches from top the bottom so I can check of them. Since every branch is lifted to the top am I not sure what branches I have already checked and which not. It would be nice if the active branch is just marked by [v] and stayed at it`s place in the list.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:8 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
iAmWillShepherdcommented, Mar 14, 2018

I understand how having a list that is always reorganizing itself can be confusing. I think we should not try to group branches by access date unless we provide alternative grouping options so that people can choose what works best for them. If we stick with trying to group branches in some way I think having them grouped into Default (should just be one branch) and Local/Remote is good enough.

1reaction
shiftkeycommented, Mar 11, 2018

This has sat for a while, and I guess the big question here from @desktop/core that I’m curious about is whether we want to revisit our thinking about the “Recent Branches” area.

Some thoughts:

  • our separation of “recent” branches from “other” might be a source of confusion when users don’t care about when a branch was last checked out locally
  • it relies on the assumption that you only care about local branches, and not branches that other users have updated recently on the remote

Personally, I’m fine with leaving it as-is until we have more insights about usage. Anything else to add?

Read more comments on GitHub >

github_iconTop Results From Across the Web

Toggle between feature request modes - ArcGIS Developers
Use different feature request modes to populate the map from a service feature ... Feature request mode is a performance concept unrelated to...
Read more >
Feature request: Page Branch - Figma Community Forum
Would be very useful to have an option to create a branch from a page. I am working on a DS and having...
Read more >
Feature request: choose source branch · Issue #213 - GitHub
My workflow is: master contains the stable releases. Every time I start working on a new release, I create a dev branch. I'm...
Read more >
Cloud Feature Requests | CircleCI Ideas
Circle CI should generate a new build when a pull request is opened on github. The current implementation uses the branch's most recent...
Read more >
Potential feature request for enhanced materials API (beware ...
I want to be able to submit very discrete pull requests but I have existing requests pending on master. I created a new...
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