code coverage environment variable

[TheAngryByrd]

Proposed Changes

Closes #138

Types of changes

What types of changes does your code introduce to MiniScaffold?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• Build and tests pass locally
• I have added tests that prove my fix is effective or that my feature works (if appropriate)
• I have added necessary documentation (if appropriate)

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

[TheAngryByrd]

@rmunn how does this look to you?

[rmunn]

I was thinking a command-line parameter, but an environment variable actually means you can "set it and forget it" in one shell session with export DISABLE_COVERAGE=1 without affecting coverage for your other shell tabs, or add it to your .bashrc if you really want to turn it off by default. And since you're already using environment variables for other things, this makes a lot of sense.

LGTM.