Long branch name is double truncated
See original GitHub issueAs of #3357 we’re supposed to be doing fancy middle truncation. But it looks like we’re really doing double truncation 🤔
The branch name is ignore-menu-events-when-modal-showing
.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Regression in 8.7 with merge request UI - long branch names are ...
With the upgrade to 8.7, the UI is no longer usable in this case since the branch names get truncated. With 8.6 they...
Read more >Branch deploy failing to use branchname for url - Support
If we truncated the branch name, there would no longer be a 1:1 connection between the branch subdomain and the branch name. Connecting...
Read more >To get a prompt which indicates Git-branch in Zsh
I just redid mine since we have long branch names at work. This one will truncate with an ellipsis if it's more than...
Read more >Frequently Asked Questions - Reserve Bank of India
Truncation is the process of stopping the flow of the physical cheque issued by a drawer at some point by the presenting bank...
Read more >Trunk-based Development vs. Git Flow - Toptal
Features developed separately can create long-living branches that might be hard to combine with the main project. What's more, pull requests focus code...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah, that’s right. There were unexpected complications with putting the path truncation strategy to use in the branch button so we reverted it. I think we should close this up, the underlying problem is sufficiently captured in https://github.com/desktop/desktop/issues/4177 and the discussion in the original PR https://github.com/desktop/desktop/pull/3269#issuecomment-344648587 so I’m going to close this one out
Should this be closed now that #3598 is merged?