Rishi Verma

This ticket is for informational purposes only - work is being performed against another ticket #110 by @yunks128 and @riverma.

Thanks for the write-up diagram @jpl-jengelke! Some questions: - What's preventing, if anything, SCRUB to execute _at the test stage_ instead of _post build_? I think that would be a...

@lylebarner - had a few questions for you: - Related to [the question above](https://github.com/NASA-AMMOS/slim/issues/25#issuecomment-1452306898), do you have recommendations for how to filter for a smaller sample of SCRUB scanning results...

Thanks for the feedback and responses @jpl-jengelke! I think @lylebarner's thoughts on a potentially running scans in parallel to builds is really interesting. Perhaps it's better to run scans nightly...

Thanks for that @sharimayer. Quick question: if no source code has changed, do the nightly builds still get triggered? If not - what mechanism is used to know nothing has...

@jpl-jengelke: recommendation next steps for this ticket (two separate PR's): 1. A PR write-up containing directions for installing a GitHub Action to execute SCRUB automatically 2. A PR write-up to...

See @lylebarner's ticket over at SCRUB to help with (ii): https://github.com/nasa/scrub/issues/99

> @jpl-jengelke: recommendation next steps for this ticket (two separate PR's): > > 1. A PR write-up containing directions for installing a GitHub Action to execute SCRUB automatically > 2....

> The unity-py python github build has code coverage generation and reporting built in by using pytest-coverage and the coveralls platform for reporting. just set it up a bit ago...

> @riverma It looks like it may be a good idea to incorporate pytest-coverage into [Python Starter Kit](https://nasa-ammos.github.io/slim/docs/guides/software-lifecycle/application-starter-kits/python-starter-kit/) if not yet done. Or would it be more appropriate for a...