Updating amass config due to recent config changes #1337

rseedorff · 2022-09-02T15:34:22Z

Description

Updating the delivered amass config due to recent changes.

Test your changes as thoroughly as possible before you commit them. Preferably, automate your test by unit/integration tests.
Make sure that all your commits are signed-off and that you are added to the Contributors file.
Make sure that all CI finish successfully.
Optional (but appreciated): Make sure that all commits are Verified.

github-actions · 2022-09-02T15:36:53Z

Descriptor	Linter	Files	Errors	Elapsed time
✅ GIT	git_diff	yes	no	0.09s
✅ PYTHON	bandit	1	0	0.29s
⚠️ PYTHON	black	1	1	0.52s
⚠️ PYTHON	flake8	1	49	0.39s
⚠️ PYTHON	isort	1	1	0.13s
✅ PYTHON	pylint	1	0	1.48s
⚠️ SPELL	misspell	2	1	0.04s
⚠️ YAML	prettier	1	1	0.63s
✅ YAML	v8r	1	0	0.4s
⚠️ YAML	yamllint	1	1	0.13s

See errors details in artifact MegaLinter reports on CI Job page
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

Updating amass config due to recent config changes

2ffc925

rseedorff added scanner maintenance labels Sep 2, 2022

rseedorff added this to the v3.15.0 milestone Sep 2, 2022

J12934 approved these changes Sep 2, 2022

View reviewed changes

rseedorff merged commit 6a415ef into main Sep 4, 2022

rseedorff deleted the maintenance/amass-update-config branch September 4, 2022 09:39