What’s our preferred pattern on `.dockerignore` f...
# contributing-to-airbyte
c
What’s our preferred pattern on
.dockerignore
files? I thought we had a pattern where we started with
*
and then only surgically re-added the things we explicitly wanted to make available in the dockerfiles. Got some feedback asking to go the opposite way (e.g. just ignore
build
). I don’t have a preference on this once, but I’d like us to coalesce around a standard that I will follow.