From: Sean Allred <allred.sean@gmail•com>
To: Ward Hopeman <ward.hopeman@nearearth•aero>
Cc: git@vger•kernel.org
Subject: Re: Feature Request: Ignore Tracked IDE files
Date: Wed, 22 Mar 2023 04:10:26 -0500 [thread overview]
Message-ID: <m0o7ol6ta7.fsf@epic96565.epic.com> (raw)
In-Reply-To: <94EFF553-E498-46D9-B14A-3500FEDEBB47@nearearth.aero>
Ward Hopeman <ward.hopeman@nearearth•aero> writes:
> Request: Create an Ignore section that allows for minimal IDE
> inclusion without impacting IDE settings for local users.
>
> Reason for the request: Most engineering teams share some IDE
> settings when working on code. More often than not, local IDE changes
> force engineers to resort to using "git update-index --skip-worktree
> <file>” to avoid the IDE settings files from showing up. It would be
> nice to be able to identify IDE files that you want in the repository
> but not necessarily track all changes as most of them are not desired
> when individuals make those changes for local setup. But teams like to
> track and have available generic shareable configurations like tabs to
> space and line length etc. By making it a user configurable section of
> ignore it allows for future IDEs to be listed without impacting the
> way it works for common IDEs today.
It sounds like you are rather after 'public' vs 'private' IDE settings,
which would be a feature of the IDE -- not of Git -- and it seems a far
simpler model. Public settings are checked-in, private settings are not,
and private settings override public settings.
This is used by Visual Studio (IIRC) and possible in other tools (Emacs
I know for sure, though I can't imagine VS Code doesn't have this
concept by now). It's even the model used by Git itself for some things
(.gitignore vs. .git/info/exclude vs. core.excludesfile).
Are these alternative approaches not an option?
--
Sean Allred
next prev parent reply other threads:[~2023-03-22 9:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 19:49 Feature Request: Ignore Tracked IDE files Ward Hopeman
2023-03-22 9:10 ` Sean Allred [this message]
2023-03-22 13:54 ` Ward Hopeman
2023-03-22 13:55 ` Sean Allred
2023-03-22 14:21 ` Ward Hopeman
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=m0o7ol6ta7.fsf@epic96565.epic.com \
--to=allred.sean@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=ward.hopeman@nearearth$(echo .)aero \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox