.gitignore is not enough
- From
- Aleem Zaki <aleemzaki@gmail.com>
- Date
- Aug 3, 2023, 03:23 UTC
- Message-ID
- <CA+sf2-+499Nfu00ciJeLwjRmBE7Bb-WZcZuCXY2-JXs88Pwz-w@mail.gmail.com>
There are files which one would like to pull from a remote branch but not have git register said person's changes on said files
Let's have a file named: .gitpullfromremotebutdonotregistermylocalchanges
Of course, we can think of a better name
By register I mean detect, like when git status detects changes that are not staged for commit
Use case:
On GitHub, you clone a repo with a default config file (skeleton) You custom the config file with personal tokens and values If the config filename was in .gitpullfromremotebutdonotregistermylocalchanges Then the following don't have to be worried about: 1. The developer (the remote branch maintainer) doesn't have to not have a default config file (skeleton) because it was in .gitignore 2. Pushing your secrets
-- Anonymous