(Semi)-automatic way to add ignore clauses to installed dependencies in a CommandBox-driven project

Description

Scenario:

Small project in CommandBox. CB mainly spins up and down the server, CF codebase is in Git/Hg and has a .gitignore resp .hgignore file. There's a server.json

I install testbox as a dependency and get a box.json with the dependency:

 

Now, my unversioned/untracked file list in my DVCS is throwing a hissyfit because of the testbox directory. I now need to manually edit my ignore file and sort it that way.

In practice, I can't think of any scenario in which you'd want testbox in your DVCS. There are others where this assumption is not true. It's a library, unless I make modifications to it, I'd want it to be treated like a Node library that ends up somewhere in an already ignore node_modules directory.

Better behaviour:

There would be a command-line switch available to the install command that adds the install path of a library to an existing ignore file (both .gitignore and .hgignore have the same syntax - not sure if there's anything that's commonly used by these two).

So, when I create the dependency from the shell by installing it, I can determine if I want it to be ignored right away or not.

Assignee

Unassigned

Reporter

Kai Koenig

Labels

None

Affects versions

None

Fix versions

None

Priority

Major
Configure