Sometimes or at least one time you’ll need them:
Language: Comments — Documentation — Puppet Labs.
Something I am using for some of my projects:
Using multiple remote repositories with Git | David Murphy.
Still most of the time I prefer to use a private GitLab repo until I decide I can show the modifications to the world on GitHub.
Sometimes I need to have a different app configuration when running the same app under different environments.
The best way for me while working both with a local Vagrant configuration and a custom configured production environments is to use:
git update-index --assume-unchanged path/to/file.txt
The full information can be found here: Ignoring files · GitHub Help.
Don’t put the config files in .gitignore, just change them locally and update-index. If there is a newer version of the file coming from the remote repo, you will be notified and will not miss update.
One thing that I needed today. I used the last one suggested:
git ls-files -o -i --exclude-standard
and it worked well!
To see all of it: Show ignored files in git – Stack Overflow.
Nice one if you need a `clean log/history` or just need to `hide` some bad commits before the good one.
Git: Squash your latests commits into one — ariejan de vroom.
REST API Tutorial.
REST API. What is it and best practices.