I'm curious about how different companies approach the repo creation task (can you create infinite private repos? Do you have to ask for permission? etc..) and how many have a fixed naming convention.
Ask HN: What's Your Company's Repository Naming Convention?
1–4 of 4 posts
Re: Ask HN: What's Your Company's Repository Naming Convention?
#2The company i work for ha2e something like "XYZ Applications".
The %20 in the url irks me every fricken time.
I prefer kebab-case on my projects.
Re: Ask HN: What's Your Company's Repository Naming Convention?
#3The company i work for ha2e something like "XYZ Applications". The %20 in the url irks me every fricken time. I prefer kebab-case on my projects.
Azure DevOps allows that space. Fricken dorks.
Re: Ask HN: What's Your Company's Repository Naming Convention?
#4I think it's per team and you can create as few or as many repos as you like.
At my last job naming was a free-for-all for a while but then someone stepped in so that we didn't end up with endless obscurely named microservices.