AlanMattano Posted September 11, 2021 Report Share Posted September 11, 2021 The text overlaps and covers the branch. For a new user is hard to understand, find and select the branch. By the way if the info pops up (image right) that the Comments text is more visible and if possible on top in first place. Link to comment Share on other sites More sharing options...
Jaime Finat Posted September 13, 2021 Report Share Posted September 13, 2021 Dear AlanMattano, Thank you for posting your feedback here. I can confirm this occurs when: The branch length is short (as the name of the branch, displayed as a label with some alpha on top, will fit the length of the branch itself) The branch name is long. There are several branches forking from the same changeset I am reporting this issue to the development team. By now, I would kindly recommend you to consider shorting your branch names (maybe by using an incremental identifier) and type the verbose details in the comments box. You may lose some detail on the branches view, but you will ease the navigation. Thank you again for your feedback and do not hesitate to contact us in case you find something else. Best 1 Link to comment Share on other sites More sharing options...
AlanMattano Posted October 8, 2021 Author Report Share Posted October 8, 2021 (edited) Thanks, Jaime Finat! To Developers: I really love an informative exposed descriptive title instead of few letters. Since Version control has sostitude my internal changelog, release note, software changes Readme.txt , Is important to understand what the brunch title is working like the revision history update notes does, so that for me without the need for hovering or clicking on it. Is important to exposed descriptive titles because version control is the modern history updates README. Edited October 8, 2021 by AlanMattano better explanation Link to comment Share on other sites More sharing options...
calbzam Posted October 8, 2021 Report Share Posted October 8, 2021 Why don't you use a branch comment to describe the task details? Internally we prefer to use a number to name the branches "SCM1234". This number fits with the issue tracker id for the specific task. Regards, Carlos. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now