mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "BARDOT Jérôme" <>
To: Jeff King <>
Subject: Re: Questions, improvements
Date: Wed, 20 Oct 2021 14:25:32 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 19/10/2021 23:31, Jeff King wrote:
> On Tue, Oct 19, 2021 at 07:38:16PM +0200, BARDOT Jérôme wrote:
>> 1)
>> Why git not embed by default some gitinore rules (and can be "disable"
>> after).
>> All the time i have to add all operating system stuff, all editor stuff.
> I think you may have a hard time getting people to agree on what should
> go into those rules. ;)

Yes but for certain things i think we will are most of us agree. (In
professional context)

Temp files for Operating System, file system, text editor and IDE.

It can be also a great way to improve interoperability (between tools)
and identify/improve tools without personnal and team configuration.

Keep repositories clean and easily usable with an abstraction layer of
tools used to do things (editor, OS, CI, etc) is what i want. 

> But you may find core.excludesFile (documented in "git help config")
> helpful. You can set up your personal set of files once, and they will
> be used in every repository.
>> 2)
>> I need a domain name / uri / ip base way to choose auth information.
>> i find some examples in past but not as smart as what i want. (Maybe i
>> miss something)
>> 3)
>> For auth client side can we use tools like Pass and or identity manager.
> I'm not entirely sure I understand your questions here, but I think
> you're looking for credential helpers? Try "git help credentials" for an
> overview.
you understand well
> There are helpers which interact with common OS secure storage systems
> (like osxkeychain, libsecret, etc). But you can also write your own
> little scripts, and restrict them based on URLs.
> So for instance I use this config to pull a GitHub PAT out of the "pass"
> tool:
>   [credential ""]
>   username = peff
>   helper = "!f() { test $1 = get && echo password=`pass github/token`; }; f"

Look great i will test

> -Peff

  parent reply	other threads:[~2021-10-20 12:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-19 17:38 Questions, improvements BARDOT Jérôme
2021-10-19 21:31 ` Jeff King
2021-10-20 11:42   ` Johannes Schindelin
2021-10-20 12:40     ` BARDOT Jérôme
2021-10-21  0:39       ` brian m. carlson
2021-10-20 12:25   ` BARDOT Jérôme [this message]
2021-10-21  1:00     ` brian m. carlson

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).