# Reuse StackHawk apps across scans; env names group finding history, new envs orphan it

## TL;DR

Do not create a new StackHawk Application per scan or per branch. Create the app once (`hawk create app --name [repo] --env [env]`), then reuse it: environments are the grouping unit, and findings compare scan-to-scan within the same env. Pick env names deliberately (Development, CI, Staging, Production): scanning the same code under a new env name orphans your history and every finding shows up as NEW again.

Use this when you run into the situation in the title.

**When not to use this skill:** unrelated tasks. It covers only the procedure above.

## Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

## Details

Also respect the finding lifecycle (NEW, FALSE_POSITIVE, RISK_ACCEPTED, ASSIGNED): triage through the platform (`hawk op scan triage`) rather than deleting apps to clear findings.