I've added `circleci-commitlint-step` because it *should* handle linting of the appropriate
commitlint ranges via a specialized Docker container for CircleCI with a commit range.
#13
This removes `semantic-commitlint` from both the local build pipeline and the CI build pipeline. The
original value of `semantic-commitlint` was that it would handle linting only the relevant commits,
i.e. the commit range under review for a PR. However, the library doesn't seem to respect our
altered `commitlint` rules, so we'll be switching to an alternate strategy to handle linting of
specific ranges.
#13
Since we don't have any tests yet, we want to make sure the build runs successfully on all branches.
That way we can at least verify that the build works correctly.
closes#13
I finally figured it out. Restoring the cache was trying to restore the cache from an older build
that used a different image in which the root user was the one doing all the tasks. I'm pushing a
build that doesn't restore the cache, then I'll add those steps back in after the next build.
Switching back to container because I have no idea how to fix the errors that came up without them.
Additionally, I'm changing the working directory to `~/tmp` to see if that works better than the
`~/app` folder.
This adds a CircleCI config file based on the same config I use for my own website. It makes it easy
to have multiple steps running in parallel, such as running tests and coverage reports.
