From: Junio C Hamano <gitster@pobox.com>
To: Elsie Hupp <git@elsiehupp.com>
Cc: git@vger.kernel.org
Subject: Re: Multiple --global config workspaces?
Date: Mon, 10 Oct 2022 22:50:22 -0700 [thread overview]
Message-ID: <xmqqwn96x61t.fsf@gitster.g> (raw)
In-Reply-To: <C4E3A512-2E2C-4EA5-9F2E-3662BCF0F165@elsiehupp.com> (Elsie Hupp's message of "Mon, 10 Oct 2022 23:06:32 -0400")
Elsie Hupp <git@elsiehupp.com> writes:
> I structure my cloned repositories based on the remote host, e.g.:
>
> ~/Repositories/github/cloned-repository-name
> ~/Repositories/gitlab/other-cloned-repository-name
The above is by definition not "global" (aka "per user").
"--global" is for things that are of your personal preference, not
"when I am working on this project, these settings apply" (which is
suitable for "per repository").
What you want is a way to say "when I am working on these projects,
these settings apply".
One way to do this would be to have
[includeIf "gitdir:~/Repositories/github/"] path = $HOME/.githubconfig
[includeIf "gitdir:~/Repositories/gitlab/"] path = $HOME/.gitlabconfig
in $HOME/.gitconfig and then write in these two extra files that are
conditionally included whatever settings you want to use for any and
all repositories that come from GitHub or GitLab.
$ git help config
and look for Conditional includes, perhaps?
next prev parent reply other threads:[~2022-10-11 5:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 3:06 Multiple --global config workspaces? Elsie Hupp
2022-10-11 5:50 ` Junio C Hamano [this message]
2022-10-11 13:13 ` Jeff King
2022-10-11 16:55 ` Elsie Hupp
2022-10-11 18:41 ` Elsie Hupp
2022-10-14 19:39 ` Jeff King
2022-10-15 10:56 ` Matthias Aßhauer
2022-10-15 18:14 ` Jeff King
2022-10-18 4:02 ` Elsie Hupp
2022-10-18 20:53 ` Jeff King
2022-10-20 2:29 ` Elsie Hupp
2022-10-20 2:39 ` Elsie Hupp
2022-10-11 13:56 ` Philip Oakley
2022-10-11 5:51 ` Reto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqwn96x61t.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@elsiehupp.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.