Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • TortoiseGit TortoiseGit
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 382
    • Issues 382
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TortoiseGitTortoiseGit
  • TortoiseGitTortoiseGit
  • Issues
  • #2015
Closed
Open
Issue created Aug 02, 2015 by Sven Strickroth@mrtuxOwner

Save and load ref lists (selections) in "Show log" -> "Browse references"

By davide.by.z... on November 22, 2013 01:43 (imported from Google Code)


(The actual feature request is the last paragraph below.)

When working on a branch, I tend not to merge it back into master, but rather to rebase it, because I don't want to slow down my workflow to think of the best way to cleanly describe the changes-in-progress (especially since git makes it very hard to edit log messages) and to decide at exactly which points to make commits. As a result, I end up with basically two types of hanging branches:

  1. Branches that I'm keeping only for historical reference, either because the problem ended up being solved a different way, or because they were rebased into master.
  2. Branches that have yet to be dealt with, and have changes in them that I plan to complete eventually, and rebase into master.

Neither type is meant to be well-organized, but rather, represents how I actually worked on the problem. How I want to present the work is usually not the same, hence the rebasing.

Most of the time I don't want type #1 (closed) to clutter my view, but I certainly want to see those of type #2 (closed). I just learned that it is possible in "Show log" to show a custom set of branches:

  1. Click the text underlined in blue on the upper-left of "Show log" (e.g. "<All Branches>"), which opens the "Browse references" dialog
  2. Select a list of branches by either scrolling through and Ctrl+clicking them, or by Ctrl+arrow-key'ing through and Ctrl+Space'ing them, and click OK.

But as currently implemented this is not such a great solution, because the list will be forgotten the moment I close that instance of "Show log".

Proposal: Provide a way of saving and loading selections in "Browse references". This could be done in a very bare-bones fashion, just by adding a "Save" and "Load" button to the dialog, and it would be good enough to tide me through for a long time.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking