.gitignore is toothless
See original GitHub issuemyhosts
blacklist
whitelist
readmeData.json
hosts
hosts-*
are in repo, what means that .gitignore has no effect and is merely confusing - modifications to this files are still displayed by git
See https://stackoverflow.com/a/7072230/4130619 and https://stackoverflow.com/a/40272289/4130619 for some potential options
see https://github.com/StevenBlack/hosts/commits/master/.gitignore
As workaround everybody may run git update-index --skip-worktree readmeData.json
etc.
Issue Analytics
- State:
- Created 5 years ago
- Comments:14 (11 by maintainers)
Top Results From Across the Web
JBowns/toothless: Automate the publishing of your ... - GitHub
Toothless. Automate the publishing of your containerised monorepos. IMPORTANT: This tool should ONLY be run from within a container, running it outside may ......
Read more >Why is .gitignore not ignoring my files? - Stack Overflow
.gitignore just ignores files that have not yet been added to the repository. If you have already git added certain files, their modifications ......
Read more >Hemio e. V. / edentata - GitLab
A toothless web frontend for the web-service management carnivora. ... .gitignore .travis.yml · CHANGELOG.
Read more >~romi/hmmm: .gitignore - Sans Fontières Development git
092dcffa — Romi Hervier fix: added samterm theme for toothless :^) 4 months ago. 1 2 3 4 5. zig-*/ build.ninja .ninja_* tools/...
Read more >Popular "maintainer:e_a_merin" JavaScript packages | Skypack
react-gitignore. Quick .gitignore file for your react project. Updated July 25, 2019 by @e_a_merin ... Updated June 20, 2019 by @toothless ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
What I currently do to update the code and the sources, is:
Is this the best/recommended day-to-day practice, as long as things are the way that they are?
Wouldn’t it be better to either a) only distribute source changes through Git and remove the possibility for updating locally, or b) don’t distribute through Git and let people update locally?
It would be interesting to hear the reason for this Winnie-the-Pooh approach, with its disadvantages.
@matkoniecz PR are welcome as you know!