Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I like the <feature/featurename> naming scheme because in some Git software (at least in Visual Studio) all of the branches starting with <feature/> will show up in a collapsable folder named feature in the interface.



My team found slashes to be annoying though, they are illegal in docker tag and DNS names. Tagging images with branch names and creating instances with branch as subdomain is kinda convenient.


I do the same, and this seems to work in a lot of UIs for grouping git branches, with Azure DevOps being another off the top of my head.

I usually use "feat/my-branch" or "fix/my-branch" depending on the purpose of the branch.


That's one of the reasons I like it too. feature/ticketid-short-description makes it super easy to determine what the branch is for and what originated it as well as keeps it organized in most Git GUI clients




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: