IMHO the name should inform a person who sees it (a developer or user - whoever) that it's not for them. So a name like .empty or .ignore is helpful. But it would be nice to give more info - it could be done via a longer name, or perhaps there could be a brief explanation in the file along the lines ot
The purpose of this file is to keep this directory from being empty so the directory will be retained in the git repository. The directory is used by the backend code for some scripts used during provisioning, and so needs to be retained. --henry On Mon, May 14, 2018 at 4:39 PM, Mike Jennings <[email protected]> wrote: > There are a number of empty directories under the backend code that are > used for placing scripts that automatically get executed during certain > provisioning stages > > We plan on putting a empty file in each of these directories so that the > directory structure will be persisted to the git repository. > > The current thought is to use something like ".empty" as the file name to > commit to the repository, then have this file ignored in the management > node code. > > We could also use the ".gitignore" file, but this is really not what we are > trying to accomplish here. > > Does anyone have thoughts on what a preferred way to do this would be. > > Thanks, > > Mike Jennings >
