Skip to contentSkip to conversation

Maintaining commit.template config through clones

DISCUSSION Toby Corkindale 2 participants 4 messages Jun 15, 2016

lore
Share & tools
lore
#0 lore raw

Hi,
I'm attempting to implement Git at our company, and we currently use a commit template for CVS. I can convert this to a Git-formatted template, and set it for use with git-config commit.template ....

However, once the repository is cloned, this configuration option vanishes from .git/config

Is there a way to make configuration options sticky?

thanks,
Toby

Signature · 10 lines
Toby Corkindale
Software developer
w: www.rea-group.com
REA Group refers to realestate.com.au Ltd (ASX:REA)

Warning - This e-mail transmission may contain confidential information.
If you have received this transmission in error, please notify us
immediately on (61 3) 9897 1121 or by reply email to the sender. You
must destroy the e-mail immediately and not use, copy, distribute or
disclose the contents.
#1 lore raw
Quoted 8 lines · Toby Corkindale

I'm attempting to implement Git at our company, and we currently use a commit template for CVS. I can convert this to a Git-formatted template, and set it for use with git-config commit.template ....

However, once the repository is cloned, this configuration option vanishes from .git/config

Is there a way to make configuration options sticky?

Create or edit $prefix/share/git-core/templates/config.

-- Hannes

#2 lore raw
Quoted 11 lines · Johannes Sixt
Quoted 8 lines · Toby Corkindale

I'm attempting to implement Git at our company, and we currently use a commit template for CVS. I can convert this to a Git-formatted template, and set it for use with git-config commit.template ....

However, once the repository is cloned, this configuration option vanishes from .git/config

Is there a way to make configuration options sticky?

Create or edit $prefix/share/git-core/templates/config.

Thanks.
Will that keep the commit-template propagated even when the repo is cloned from another machine? (ie. using git: or ssh: methods)

tjc.

Signature · 10 lines
Toby Corkindale
Software developer
w: www.rea-group.com
REA Group refers to realestate.com.au Ltd (ASX:REA)

Warning - This e-mail transmission may contain confidential information.
If you have received this transmission in error, please notify us
immediately on (61 3) 9897 1121 or by reply email to the sender. You
must destroy the e-mail immediately and not use, copy, distribute or
disclose the contents.
#3 lore raw
Quoted 9 lines · Toby Corkindale
Quoted 8 lines · Johannes Sixt
Quoted 7 lines · Toby Corkindale

I'm attempting to implement Git at our company, and we currently use a commit template for CVS. I can convert this to a Git-formatted template, and set it for use with git-config commit.template ....

However, once the repository is cloned, this configuration option vanishes from .git/config

Quoted 7 lines
Quoted 3 lines
Quoted 1 line

Is there a way to make configuration options sticky?

Create or edit $prefix/share/git-core/templates/config.

Thanks.
Will that keep the commit-template propagated even when the repo is cloned from another machine? (ie. using git: or ssh: methods)

No. You have to edit this file on each machine.

-- Hannes