Tyler D

Run homebrew formula locally in pipeline prior to publish

1

Before releasing our homebrew formula, we should test it locally in the pipeline. This should be done prior to executing `secureli-deployment.sh` [in the pipeline](https://github.com/slalombuild/secureli/blob/main/.github/workflows/publish.yml#L142). This is probably best done as...

1. We should start using unique exit codes to differentiate between reasons for exiting (e.g. failing a scan versus versus failing due to an exception). 2. Scan failures are the...

As a SeCurLI user, I want SeCurLI to simulate the behavior as if it were running in the main branch.    So that we can correct our semantic-release dry-run step [HERE](https://github.com/slalombuild/secureli/blob/main/.github/workflows/build_and_test.yml#L69)...

Document usage of config files

2

In `CONTRIBUTING.md`, we should add an introductory explanation of the various configuration files we use (`.secureli.yaml`, `.secureli/repo-config.yaml`, and `.pre-commit-config.yaml`). This should include the reasoning for splitting configuration across these files,...

When seCureLI writes a `.pre-commit-config.yaml` file, it does not recognize or respect any existing contents if that file already exists. We should merge the YAML with existing hooks. We also...

Instead of pulling down [pip](https://github.com/pypa/pip) on every commit to `main`, we should be caching the results so we can avoid pulling down the same repo frequently. This should speed up...