-
|
Is there a good way to know how old a branch is relative to the target branch? Specifically talking the branches page. With GitHub they have a I know it isn't an absolute measurement, but could help indicate how easy it would be to integrate the commits from that branch. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Thanks a lot for sharing! Right now, GitButler doesn't have a way to provide this kind of essential information in the workspace view, unfortunately. There is the notion of commits ahead in the branch view…
…but unfortunately there is no commits-behind information. In the workspace view, there is a notion of how many commits the whole workspace is behind, at most:
But in future, that actually applies to every stack individually as we don't rebase stacks onto the workspace base anymore, so each of them has their own relationship with the target branch. Let me CC @krlvi and @OliverJAsh for this as now seems to be a good time to keep that in mind. |
Beta Was this translation helpful? Give feedback.


Thanks a lot for sharing!
Right now, GitButler doesn't have a way to provide this kind of essential information in the workspace view, unfortunately. There is the notion of commits ahead in the branch view…
…but unfortunately there is no commits-behind information.
In the workspace view, there is a notion of how many commits the whole workspace is behind, at most:
But in future, that actually applies to every stack individually as we don't rebase stacks onto the workspace base anymore, so each of them has their own relationship with the target branch.
Let me CC @krlvi and @OliverJAsh for this as now seems to be a good time to keep that in mind.