Pin branch to left in the graph 📌

Comments: 34

Oldest • Newest • Most likes • Fewest likes

• Add a comment
• 21 Mar, '24
  David

  Highlighted comment
  
  Yes, please! I can't imagine a feature I'd want more than this.

  3 Copy link to this comment
• 03 Mar
  Jonathan Admin Pinned

  Jonathan from the GitKraken team here. This has been one of the most-requested graph improvements we've tracked. I count ~431 votes and years of detailed feedback!
  
  It's here. As of GitKraken Desktop 11.10, you can now pin any branch to the left side of the Commit Graph.
  Right-click any branch (in the graph or the Left Panel) and select "Pin to Left." From that point on, all commits in that branch's
  direct history will always render on the left side. No more hunting for main or prod in a busy graph. Right-click the branch
  again to unpin at any time.
  
  This is especially useful for default branches, production branches, and anywhere you need to see how work is being merged
  in, directionally, at a glance.
  
  Full release notes: https://help.gitkraken.com/gitkraken-desktop/current/#version-11-10-0
  Download the latest version: https://www.gitkraken.com/download
  
  Thank you for the patience and the specific, detailed feedback that shaped exactly how this was built.

  Copy link to this comment
• 22 Jun, '21
  Rob Merged

  I often adopt very messy repos where best practices are inconsistent or non existent. It would be very helpful to be able to pin a specific branch to the left side of the Commit Graph. This would make it easier to visually follow the flow or commits in and out of a Base or Main Branch without having to solo it.

  3 Copy link to this comment
• 22 Jun, '21
  Giacomo Zanotti System

  "Add the ability to pin a specific branch to the left side of the graph view without soloing" (suggested by Rob on 2021-06-22), including upvotes (1) and comments (0), was merged into this suggestion.

  2 Copy link to this comment
• 24 Jun, '21
  Appurist

  I just independently made this same suggestion in a Twitter reply. I'd love to see something done to make the behavior more predictable.
  
  I'd also be even happier to see *auto*-pinning of branch order (or default ordering) with either left-side priority given to older created branches, or right-side priority given to branches with more recent commits (perhaps a preference). Although the latter would still reorder after a merge... :(
  
  Obviously manual pinning allows any of these approaches, but there's still an opportunity to avoid the need for manual pinning at all if the default ordering of branches was based on something specific like this, and thus more deterministic. One UI problem this could avoid is the seemingly random reordering of branches after a merge.

  3 Copy link to this comment
• 09 Aug, '21
  Danny Pursley Merged

  In the GRAPH column it would be so helpful if the MASTER release was always on the far left and then DEVELOP was always the next column to the right of MASTER and then features continued out to the right of that. Currently it seems random where the MASTER and DEVELOP paths are located making it more difficult to follow what branch is MASTER and which one is actually DEVELOP, etc.

  5 Copy link to this comment
• 09 Aug, '21
  Giacomo Zanotti System

  "Organize GRAPH Column" (suggested by Danny Pursley on 2021-08-09), including upvotes (1) and comments (0), was merged into this suggestion.

  2 Copy link to this comment
• 14 Sep, '21
  Morgan Scruggs Merged

  an option to keep master branch on the left or right of the tree to make it easy to follow.

  1 Copy link to this comment
• 14 Sep, '21
  Giacomo Zanotti System

  "option to show master branch always on one edge of the tree" (suggested by Morgan Scruggs on 2021-09-14), including upvotes (1) and comments (0), was merged into this suggestion.

  2 Copy link to this comment
• 10 Dec, '21
  Kouji Matsui

  Oh, I understand why harder tracking branch history on my job repos. It causes by git-flow like branch management. I'm strongly upvote supporting this in near the future GitKraken!

  1 Copy link to this comment
• 09 Feb, '22
  Bernd Wechner

  I would request that we be able to ping one or two branches to the left as straight lines bottom to top with the rest as branches off to the right and between these two.
  
  These can map very elegantly to the two dominant branches most project manage, the master/main branch and the development branch.
  
  Whichever one is checked-out I would argue should be leftmost, and the other beside it to the right.

  1 Copy link to this comment
• 16 Feb, '22
  Chris Roberts

  I would love to be able to pin the main/master branch to the left of the tree. I'm working with a slightly odd git repo which has many small branches that are all getting contributed to regularly. I often lose the master branch within the others as they await to be validated and merged in.

  1 Copy link to this comment
• 05 Mar, '22
  Steve

  I'd like to add my upvote to this request, it'd be very handy!

  1 Copy link to this comment
• 08 Apr, '22
  Jason Persson

  I badly want this. My workplace refuse to use a linear history because of the perceived difficulty of rebasing. Jetbrains IDEs and the **free** git extensions are able to do this.

  1 Copy link to this comment
• 21 Jul, '22
  Nathan

  Great idea, in our git flow there are few "static" branches that could be pinned (dev, release-candidate, prod)
  and many temporary branches (features, and fixes)
  being able to pin the static branches can simplify significantly the graph complexity and the constant movement of the branches.
  ---
  would be nice if the "pin" could work on regexes, so I can configure something like:
  branches order:
  1. dev
  2. rc/*
  3. prod
  
  were the rc refers to any branch start with rc: rc/1.1.1, rc/1.2 etc.
  
  thanks

  2 Copy link to this comment
• 09 Aug, '22
  Xorcist

  I would like to see an option for strictly time based ordering of the graph. It should be simple enough to order all the branches/nodes by creation date so that the graph is historically accurate from bottom to top, rather than the current graph which just pushes the latest worked branch to the left-most position.

  1 Copy link to this comment
• 12 Aug, '22
  Tim G

  This will make it much clearer for users where they're editing code. Muliple pins are essential - for example we have a prod and dev branch, where further branches are taken from. Some kind of left to right auto formatting may be the solution here.
  Also highlighting the 'working' branch, or allowing colour selection as well as pinning or setting left to right may be further helpful.

  1 Copy link to this comment
• 08 Sep, '22
  Sam

  I would very much like this feature. Even just a single pinned branch would help me greatly.

  1 Copy link to this comment
• 21 Oct, '22
  Ismael

  I second this!
  (I was searching for this option and found this request instead)

  1 Copy link to this comment
• 17 Nov, '22
  Carles Mitjans

  I would really like this feature as well

  1 Copy link to this comment
• 10 Feb, '23
  Jose

  Pin branch, fav branch, anything to be able to retrieve a branch easier when switching between one and another in a busy repository that has 20 employees in it. I often find myself helping others too a crtiical bugs, so highlighting my own branches is not enough, and I do not clean my local branches because I'm messy, I use the filter instead.

  1 Copy link to this comment
• 14 Feb, '23
  Chris Bowie System

  "Add possibility to PIN a branch on the origin" (suggested by Paolo Ponznao on 2023-02-11), including upvotes (1) and comments (0), was merged into this suggestion.

  3 Copy link to this comment
• 26 Jun, '23
  Rodrigo Sales

  I agree, this is what keep me using Git Extensions, there I can easily follow the current branch in the graph, it would be even more helpful if GitKraken change the branch colors based on this also (or make the other branchs with no colors like Git Extensions)

  1 Copy link to this comment
• 14 Dec, '23
  Chad

  Our company's teams would definitely use this feature, looking to pin multiple branches to the left in a configurable order per repository. As a couple examples, this would be rc,dev,beta for most of our repos/teams, and release,uat,test,dev for others. The pinned configuration should also be visible/enabled by all GitKraken users to save the same configuration from having to be done on N systems for X repos. Using 30 users and 40 repos as an example, this would mean 1 person configuring this 40 times instead of 30 people configuring it 40 times for a total of 1200 configurations.

  3 Copy link to this comment
• 24 May, '24
  JWT

  Also upvoted... came here looking for exactly this suggestion! :)

  3 Copy link to this comment
• 13 Sep, '24
  Mad User

  I dont understand how on earth after so long they dont have a simple reordering or pining of the local branches at least. This is absurd. Local branches are all over the place, ordered god knows how. Main branches in the middle of various folders while they should always be at the top. Just for this nonsense I am thinking of cancelling the subscription as this just shows how they dont give a shit about any useful suggestions. This suggestion has over 300 upvotes and its been 3 fucking years.

  5 Copy link to this comment
• 10 Oct, '24
  karol

  i would love that! im waiting for so long
  pinning or ordering would be great, especially when in-sync with branch tree on left side

  4 Copy link to this comment
• 27 Jan, '25
  Andrej Rypo

  this seems like a duplicate of this one : https://feedback.gitkraken.com/suggestions/347190/add-favorite-or-pinned-branches-in-the-left-sidebar

  1 Copy link to this comment
• 01 Aug, '25
  kriboogh

  A fixed order from left to right for branch name patterns would be nice yes. just as an example:
  master
  hotfix/*
  release/*
  develop
  feature/

  2 Copy link to this comment
• 18 Sep, '25
  Jeremiah Snee

  Create a feature request with minimal/ incremental improvement
  https://feedback.gitkraken.com/suggestions/666733/showing-default-branch-at-the-top

  2 Copy link to this comment
• 01 Dec, '25
  mrfour

  In a complex repository, it is challenging to track commits on a specific branch if they are not consistently positioned on the left side. I have eagerly anticipated this fix (or feature) for several years, but it remains a persistent issue for me.

  3 Copy link to this comment
• 18 Dec, '25
  Frank Pfattheicher Merged

  Very much repos opended.
  My GitKraken most times looks like the picture attached.
  No repo name is visible :-(
  
  An option to place these tabs on the left and let me drag the size would improve usability a lot.

  Copy link to this comment
• 05 Jan
  Chris Bowie System

  "Option to show repo tabs on the left" (suggested by <Hidden> on 2025-12-18), including upvotes (1) and comments (0), was merged into this suggestion.

  

  1 Copy link to this comment
• 06 Feb
  karol

  finally in development :pray::thank_u:

  2 Copy link to this comment