Search code examples
gitnaming-conventionsgit-config

Git - naming conventions in .config?

I searched, but could not find if there is agreed naming convention for git configuration options and alike?

For example, opening typical git .config file, you can see options like repositoryformatversion or logallrefupdates. Those are not camelCase nor snake case. Is it recommended to use such convention (as seen by default options) when adding your custom config options?

Solution

  • As phd said in a comment, there is no standard here. Note that when Git looks things up internally, it just converts everything to lowercase, using the C language tolower function, and then compares the results.