So, you’re changing this one file for local development purposes only. Maybe it’s config, maybe some source file, but one thing is certain - you don’t want those changes to be committed. And what’s worse, .gitignore doesn’t work.

Table of contents

    Yeah, .gitignore works only for files not tracked by git yet. So if there’s a config.ex file, which is a part of the project, and you don’t want to rebuild the repo from the foundation (which is rather a bad idea), then you probably want to reach for this one simple trick:

    $ git update-index --skip-worktree config/config.exs

    From git docs:

    Skip-worktree bit can be defined in one (long) sentence: Tell git to avoid writing the file to the working directory when reasonably possible, and treat the file as unchanged when it is not present in the working directory.

    Neither git status, git add . nor your IDE source control visualization should bother you anymore.

    Ahh, and remember two more commands if you don’t want to google them later madly:

    1. This one shows all the files you marked with the --skip-worktree flag
    $ git ls-files -v . | grep ^S
    > S config/config.exs
    1. And that’s how you tell git to remove the flag:
    $ git update-index --no-skip-worktree config/config.exs

    Happy hacking!

    Oskar Legner
    Oskar Legner Elixir & React Developer

    Read more
    on #curiosum blog

    Bringing SOLID to Elixir

    Bringing SOLID to Elixir

    The SOLID principles, originally designed for object-oriented programming, can also be adapted effectively to functional programming languages like Elixir. Read how to apply it to create more maintainable, scalable, and adaptable software systems.