.gitconfig options

[lyzadanger]

@tylersticka has pointed out that boxen doesn't write user.name and user.email to .gitconfig on fresh installs.

I believe this is probably by design, because some people don't like to put personal settings in version control, especially for folks who use public repos for boxen and/or dotfiles.

In my case, funnily enough, I was just looking at this today as part of the dotfile research I'm doing. There is a small subset of stuff I'd like to keep out of my public dotfiles repo (lyzadanger/dotfiles), and git user information is in that small subset (the other stuff in my .lyza file is a couple of aliases specific to my directory structure).

We have a few potential paths we can take on this:

We could skip automating .gitconfig setup for personal data but instead make it a documented setup step to take. This leans toward privacy protection but is not as efficient.

Alternately, we can add git credentials to everyone's personal modules, using this pattern:

git::config::global { 'user.email':
  value  => 'turnt@example.com'
}

And as a final option, those of us cozy with managing our own hoo-hah can use version-controlled dotfiles/whatnot for this stuff.

Y'alls input is solicited.

/cc @erikjung @tylersticka @lharding

[erikjung]

An install script that takes the info from stdin.

Sent from my iPhone

On Jan 26, 2015, at 4:04 PM, Lyza Gardner notifications@github.com wrote:

@tylersticka has pointed out that boxen doesn't write user.name and user.email to .gitconfig on fresh installs.

I believe this is probably by design, because some people don't like to put personal settings in version control, especially for folks who use public repos for boxen and/or dotfiles.

In my case, funnily enough, I was just looking at this today as part of the dotfile research I'm doing. There is a small subset of stuff I'd like to keep out of my public dotfiles repo (lyzadanger/dotfiles), and git user information is in that small subset (the other stuff in my .lyza file is a couple of aliases specific to my directory structure).

We have a few potential paths we can take on this:

We could skip automating .gitconfig setup for personal data but instead make it a documented setup step to take. This leans toward privacy protection but is not as efficient.

Alternately, we can add git credentials to everyone's personal modules, using this pattern:

git::config::global { 'user.email':
value => 'turnt@example.com'
}
And as a final option, those of us cozy with managing our own hoo-hah can use version-controlled dotfiles/whatnot for this stuff.

Y'alls input is solicited.

/cc @erikjung @tylersticka @lharding

—
Reply to this email directly or view it on GitHub.

[tylersticka]

It might also be useful just as part of "new hire" documentation (maybe as a follow-up to SSH stuff).