Landing a Pull Request (PR)

Long form explanations of most of the items below can be found in the CONTRIBUTING guide.

Branching checklist

[ ] There is an issue associated with your PR (bug, feature, etc.. if not, create one)
[ ] Your PR description references the associated issue (i.e. fixes #123456)
[ ] Code is in its own branch
[ ] Branch name is related to the PR contents
[ ] PR targets main

Static analysis checks

[ ] All rust files are formatted using cargo fmt
[ ] All clippy checks pass when running cargo clippy --all-targets --all-features -- -D warnings -A clippy::mutex-atomic
[ ] All existing tests pass

Documentation

[ ] New code is documented using doc comments
[ ] Documentation about your PR is included in the docs, as needed. The docs live in a separate repository. Update the appropriate pages at the links below.
- [ ] update example config file section
- [ ] update help output section
- [ ] add an example
- [ ] update comparison table

Additional Tests

[ ] New code is unit tested
[ ] New code is integration tested, as needed
[ ] New tests pass

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 92.54%. Comparing base (38a1ed3) to head (22f2948). Report is 5 commits behind head on main.

:exclamation: Current head 22f2948 differs from pull request most recent head f7a22d2. Consider uploading reports for the commit f7a22d2 to get more accurate results

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #1072 +/- ## ========================================== + Coverage 92.34% 92.54% +0.19% ========================================== Files 63 63 Lines 12103 12355 +252 ========================================== + Hits 11177 11434 +257 + Misses 926 921 -5 ```

epi052 / feroxbuster

parallel time limit enforced individually instead of main thread #1072