3 ms·
I fall somewhere in between. I don't mind if the names are random and fun. But I do like: - avoiding the use of slashes (because with enough folks working on th
by abhorrence 6y ago
I fall somewhere in between. I don't mind if the names are random and fun. But I do like:
- avoiding the use of slashes (because with enough folks working on the same repo, you can get some crazy conflicts)
- prefixing with some sort of "handle" (e.g. your initials) to help avoid branch name conflicts
- craigmcnamara 6y agoYea, the slashes in branch names grates on me because '/' is a character that means too many things and the name winds up in URLs on Github.
- battery_cowboy 6y agoI made it a policy to only use a-z, 0-9, and _ in any branch, file, folder, or any other 'names' in the cli. Basically anything I'd type in the cli as an identifier/name. I find it prevents weird issues with characters when scripting and such, since the rest of the shiftable symbols on the 1-0 row (*, &, etc.) tend to cause issues when used too much in names because they're also used as operators and stuff. I think I started doing that with Windows filenames, since it has so many limits, and it crossed over into my Linux cli workflow.