Recommended setup

We recommend adding as the first step in your GitHub actions workflow file. This will allow you to inspect the behavior of all proceeding steps in the workflow run.

Currently requires a manifest file to be present in the root of your project, in order to understand how dependencies are assembled inside your codebase. See the specific guidance below:

For JavaScript projects

  • npm package manager using package-lock.json

For Python projects

  • pip package manager using poetry.lock as manifest file

By default, the manifest is read from the root of the repository, or {{ github.workspace }} You can also add custom paths using the workdir: option in the GitHub actions workflow step, or by using the .lstn.yml config file.

Last updated

© 2024 Garnet Labs