Getting started with the Moderne CLI

The Moderne CLI is a command line tool that compliments the Moderne Platform and Moderne DX, enabling you to build Lossless Semantic Tree (LST) artifacts across many repositories and run recipes against all of them from your local machine. It also provides substantial benefits for creating and testing your own recipes.

To ensure you can use the Moderne CLI successfully, in this guide, we will walk you through everything you need to get started – from installation, to configuration, to examples demonstrating how to use it.

Assumptions

• You can access app.moderne.io or a private Moderne tenant
• You are familiar with running terminal commands

Installation and configuration

If you are in an air-gapped environment, please follow the instructions for installing and configuring the CLI in an air-gapped environment instead.

Step 1: Download the CLI

1. Go to the Moderne Platform (or your private tenant) and sign in.
2. Click on Help in the bottom left-hand corner and select the version of the CLI you want to download (Stable or Staging).
3. Either press the download button for your appropriate OS, or select the installation method in the provided table. We recommend using HomeBrew or Chocolatey if you have access to either.

4. If you chose to install the CLI without a package manager, you'll need to save it somewhere that your terminal can access. This could involve updating your PATH to point to a specific location – or this could involve putting it in a directory that's already on your PATH (such as a /user/bin directory).
   • Remember to refresh any open terminals if you modify the PATH.

If everything was configured correctly, you should be able to type mod into your terminal and see a list of commands:

mod command results

➜ mod

Moderne CLI 3.44.4

Usage:

mod [-h] [--version] [COMMAND]

Description:

Automated code remediation.

Options:

  -h, --help      Display this help message.
      --version   Display version info.
Commands:

  afterburner          (INCUBATING) Indexes built LSTs to accelerate recipe
                         execution.
  audit                (INCUBATING) Perform an audit of recent activity.
  batch                Add batch changes to the Moderne platform.
  build                Generates LST artifacts for one or more repositories.
  clean                Clean build and run artifacts produced by the CLI.
  config               Global configuration options that are required by some
                         CLI commands.
  devcenter            Generate DevCenter dashboards.
  exec                 Execute an arbitrary shell command recursively on
                         selected repository roots.
  generate-completion  Generate bash/zsh completion script for mod.
  git                  Multi-repository git operations.
  log                  Manages a log aggregate.
  list                 Lists the repositories that can be built and published.
  monitor              (INCUBATING) Launches an HTTP server used to monitor the
                         CLI.
  publish              Publishes the LST artifacts for one or more projects.
  run                  Runs an OpenRewrite recipe locally on pre-built LSTs.
  run-history          Get information about the most recent recipe runs. This
                         will be transitioning to mod audit runs list
                         eventually. A deprecation notice will be added here
                         when we suggest adopting the alternative.
  study                Produces studies from OpenRewrite recipe data tables
                         locally.

Step 2: (Optional) Set up auto-completion in your terminal (Unix terminals only)

The Moderne CLI offers a command which generates a completion script that can be used to set up auto-completion in your terminal. After initializing this script, you can type mod config and press tab and then your terminal will offer suggestions for the sub-commands or parameters:

To configure this for the terminal you're using please enter the following command in your terminal:

source <(mod generate-completion)

Or, if you want to configure auto-completion so that it works for every terminal instance you make, please update your ~/.zshrc or ~/.bashrc file and add this command to the bottom of it:

# The next line enables shell command completion for mod
source <(mod generate-completion)

Step 3: Connect the CLI to Moderne

Connecting the CLI to Moderne is necessary to:

• Quickly sync the recipe catalog from Moderne to your local machine
• Download pre-built LSTs from Moderne so you can quickly run recipes locally
• Receive organizational information, so you can clone/build/run groups of repositories more easily

To set up this connection, you'll first need to create an access token for the CLI to use. Follow the below instructions to obtain a token and provide it to the CLI:

1. Navigate to https://app.moderne.io/settings/access-token
   • If you're in a private tenant, replace app.moderne.io with your tenant URL
2. Enter a human-readable name for the token (e.g., cli-token)
3. Press Generate
4. Copy the install on your workstation command and paste it into your command line. This command should look something like:

mod config moderne edit https://app.moderne.io --token mat-YOUR_TOKEN_HERE

5. If everything worked, you should see a MOD SUCCEEDED message

Step 4: Install recipes

With the Moderne connection established, you can download recipes to your local machine by running the following command:

mod config recipes moderne sync

info

Occasionally, a few of the recipes may fail to sync properly and return the message ! Failed to install. If the majority of the recipes installed successfully, however, you will see the MOD PARTIALLY SUCCEEDED message when the command completes, and you can still continue on without a problem for the purposes of this tutorial.

This will grab all of the recipes from the tenant you specified in mod config – so please expect this command to take a few minutes to download the recipes.

Using the CLI

With installation and configuration done, you're now ready to use the CLI. Let's walk through some things you might do with it. We recommend you follow along on your own machine to get a feel for how to use the CLI.

info

The Moderne CLI was not designed to run multiple commands simultaneously. Please only execute one command at a time.

Run recipes against many repositories at once

Building

In this example, we will use the Moderne CLI to run the DependencyVulnerabilityCheck recipe against a group of open-source repositories.

1. From your terminal, create a directory to work in and cd into it:

mkdir -p $HOME/workshop
cd $HOME/workshop

2. For this exercise, we've prepared a list of open-source repositories for you to use. These repositories have been added to the Moderne Platform and put inside the Default organization. Clone these repositories by running the following command from inside your workshop directory:

mod git sync moderne . "Default" --with-sources

warning

If you need to enter an SSH passphrase to clone repositories, please see our SSH keys with passphrases guide before continuing.

You should see output similar to the following.

Moderne CLI 3.44.4

⏺ Retrieving organization from Moderne

Found organization ALL/Default
Organization written to disk at /Users/mikesol/workshop/.moderne/repos.csv

⏺ Synchronizing organization directory structure

Adding organization Default
Adjusted 1 organization directory. (1s)

⏺ Performing Git operations on repositories

A sync log file will be written to /Users/mikesol/workshop/.moderne/sync.log

▶ aws/amazon-documentdb-jdbc-driver@develop
    ✓ Checked out fca7f5f on branch develop
▶ openrewrite/rewrite-recipe-bom@main
    ✓ Checked out 4238a21 on branch main
▶ finos/messageml-utils@main
    ✓ Checked out 3e0ba74 on branch main
▶ Netflix/ribbon@master
    ✓ Checked out 625e167 on branch master
▶ apache/maven-doxia@master
    ✓ Checked out 851f8c1 on branch master
▶ finos/symphony-wdk@master
    ✓ Checked out e965749 on branch master
▶ finos/spring-bot@spring-bot-master
    ✓ Checked out 7280971 on branch spring-bot-master
▶ finos/symphony-bdk-java@main
    ✓ Checked out faab9ef on branch main
▶ awslabs/aws-saas-boost@main
    ✓ Checked out 452d7ca on branch main
▶ spring-projects/spring-petclinic@main
    ✓ Checked out 30aab0a on branch main
▶ spring-projects/spring-data-commons@main
    ✓ Checked out ec792a2 on branch main
▶ Netflix/photon@master
    ✓ Checked out 2ee9afa on branch master
Done (11s)

⏺ Downloading LSTs for repositories

▶ finos/messageml-utils@main
    ✓ Downloaded messageml-utils-20250723145851654-ast.jar
▶ spring-projects/spring-data-commons@main
    ✓ Downloaded spring-data-commons-20250723152241873-ast.jar
▶ spring-projects/spring-petclinic@main
    ✓ Downloaded spring-petclinic-20250723152421690-ast.jar
▶ Netflix/ribbon@master
    ✓ Downloaded ribbon-20250723151801687-ast.jar
▶ openrewrite/rewrite-recipe-bom@main
    ✓ Downloaded rewrite-recipe-bom-20250723152102910-ast.jar
▶ apache/maven-doxia@master
    ✓ Downloaded maven-doxia-20250723145631700-ast.jar
▶ Netflix/photon@master
    ✓ Downloaded photon-20250723151409886-ast.jar
▶ finos/symphony-wdk@master
    ✓ Downloaded symphony-wdk-20250723150928349-ast.jar
▶ finos/spring-bot@spring-bot-master
    ✓ Downloaded spring-bot-20250723150005923-ast.jar
▶ finos/symphony-bdk-java@main
    ✓ Downloaded symphony-bdk-java-20250723150711649-ast.jar
▶ awslabs/aws-saas-boost@main
    ✓ Downloaded aws-saas-boost-20250723145823330-ast.jar
Done (7s)

Synced 12 repositories.

MOD SUCCEEDED in 20s

3. Confirm that your repositories were cloned correctly by running the following command:

ls  .  # For Mac/Unix users
dir .  # For Windows users

You should see output similar to the following.

apache          aws             awslabs         finos           Netflix         openrewrite     spring-projects

4. If the Lossless Semantic Trees (LSTs) were available to download from Moderne, then they will have been downloaded with the mod git sync moderne command. If the LST(s) were unavailable for some reason, you can generate them locally by running the mod build . command.

info

By default, the CLI is able to build LSTs for well-formed projects (i.e. projects that build well with a plain mvn verify or gradle build). At times, however, you may encounter a project that fails to build. This could be because of a hidden dependency on certain tooling, like NPM, or because specific dependencies or repositories are not available without additional configuration.

Through mod config build and other configuration options, you're typically able to get these LSTs built and ingested fairly quickly. For the purposes of this tutorial, however, let's ignore any projects that don't build and focus on running recipes against the ones that do.

mod build .

You should see output similar to the following.

Moderne CLI 3.44.4

⏺ Reading organization

Found 1 organization containing 12 repositories (1s)

⏺ Building LST(s)

▶ apache/maven-doxia@master
    Build output will be written to build.log
    > Download from Moderne
        ✓ Downloaded maven-doxia-20250723145631700-ast.jar
    Cleaned 1 older builds
▶ aws/amazon-documentdb-jdbc-driver@develop
    Build output will be written to build.log
    ✗ Failed to build an LST.
▶ awslabs/aws-saas-boost@main
    Build output will be written to build.log
    > Download from Moderne
        ✓ Downloaded aws-saas-boost-20250723145823330-ast.jar
    Cleaned 1 older builds
▶ finos/messageml-utils@main
    Build output will be written to build.log
    > Download from Moderne
        ✓ Downloaded messageml-utils-20250723145851654-ast.jar
    Cleaned 1 older builds
▶ finos/spring-bot@spring-bot-master
    Build output will be written to build.log
    > Download from Moderne
        ✓ Downloaded spring-bot-20250723150005923-ast.jar
    Cleaned 1 older builds
▶ finos/symphony-bdk-java@main
    Build output will be written to build.log
    > Download from Moderne
        ✓ Downloaded symphony-bdk-java-20250723150711649-ast.jar
    Cleaned 1 older builds
▶ finos/symphony-wdk@master
    Build output will be written to build.log
    > Download from Moderne
        ✓ Downloaded symphony-wdk-20250723150928349-ast.jar
    Cleaned 1 older builds
▶ Netflix/photon@master
    Build output will be written to build.log
    > Download from Moderne
        ✓ Downloaded photon-20250723151409886-ast.jar
    Cleaned 1 older builds
▶ Netflix/ribbon@master
    Build output will be written to build.log
    > Download from Moderne
        ✓ Downloaded ribbon-20250723151801687-ast.jar
    Cleaned 1 older builds
▶ openrewrite/rewrite-recipe-bom@main
    Build output will be written to build.log
    > Download from Moderne
        ✓ Downloaded rewrite-recipe-bom-20250723152102910-ast.jar
    Cleaned 1 older builds
▶ spring-projects/spring-data-commons@main
    Build output will be written to build.log
    > Download from Moderne
        ✓ Downloaded spring-data-commons-20250723152241873-ast.jar
    Cleaned 1 older builds
▶ spring-projects/spring-petclinic@main
    Build output will be written to build.log
    > Download from Moderne
        ✓ Downloaded spring-petclinic-20250723152421690-ast.jar
    Cleaned 1 older builds
Done (1m 26s)

24m 7s saved by using previously built LSTs

Built 0 repositories.

PARTIAL SUCCESS: mod partially succeeded with an exception

Running

With the LSTs built, you can now run recipes against them. Let's run the DependencyVulnerabilityCheck recipe to find and fix vulnerable dependencies. Unlike many other tools, this recipe can find and fix dependencies that are many levels deep. For instance, if you depend on a library which depends on a library which depends on a library which contains a vulnerable dependency, this recipe can find that and offer suggestions on how to fix it.

Note: Please make sure to pick the org.openrewrite.java.dependencies.DependencyVulnerabilityCheck recipe when you run the following command as multiple recipes with this title exist.

mod run . --recipe DependencyVulnerabilityCheck

You should see output similar to the following.

Moderne CLI 3.44.4


[1] Find and fix vulnerable Nuget dependencies (org.openrewrite.csharp.dependencies.DependencyVulnerabilityCheck)
[2] Find and fix vulnerable dependencies (org.openrewrite.java.dependencies.DependencyVulnerabilityCheck)
[3] Find and fix vulnerable npm dependencies (org.openrewrite.nodejs.DependencyVulnerabilityCheck)
Select a recipe [1-3]: 2
⏺ Reading organization

Found 1 organization containing 12 repositories (1s)

⏺ Running recipe org.openrewrite.java.dependencies.DependencyVulnerabilityCheck

Run log

▶ aws/amazon-documentdb-jdbc-driver@develop (no LST)
    Skipped recipe run because no LST was found
▶ openrewrite/rewrite-recipe-bom@main
    No changes
    ✓ Recipe run complete
▶ finos/messageml-utils@main
    No changes
    ✓ Recipe run complete
▶ apache/maven-doxia@master
    No changes
    ✓ Recipe run complete
▶ spring-projects/spring-petclinic@main
    No changes
    ✓ Recipe run complete
▶ finos/symphony-wdk@master
    No changes
    ✓ Recipe run complete
▶ Netflix/photon@master
    ⚠ The latest LST is not up to date
    No changes
    ✓ Recipe run complete
▶ Netflix/ribbon@master
    ✓ Fix results
    ✓ Recipe run complete
▶ spring-projects/spring-data-commons@main
    No changes
    ✓ Recipe run complete
▶ finos/symphony-bdk-java@main
    No changes
    ✓ Recipe run complete
▶ finos/spring-bot@spring-bot-master
    No changes
    ✓ Recipe run complete
▶ awslabs/aws-saas-boost@main
    ✓ Fix results
    ✓ Recipe run complete
Done (1m 11s)

24m 7s saved by using previously built LSTs
45m saved by using recipes

Produced results for 11 repositories.

⏺ What to do next
    > A repository's source code doesn't match its LST. Run mod build to update the LSTs.
    > Click on one of the patch links above to view the changes on a particular repository
    > Run mod study to examine the following data tables produced by this recipe:
          > mod study . --last-recipe-run --data-table VulnerabilityReport
          > mod study . --last-recipe-run --data-table MavenMetadataFailures
          > mod study . --last-recipe-run --data-table RecipeRunStats
          > mod study . --last-recipe-run --data-table SourcesFileResults
    > Run npm install -g diff2html-cli to produce patch files on subsequent runs that are easier to view
    > Run mod git checkout . -b refactor/DependencyVulnerabilityCheck --last-recipe-run to prepare a refactor/DependencyVulnerabilityCheck branch for applying the changes
    > Run mod git apply . --last-recipe-run to apply the changes
    > Run mod git apply . --recipe-run 20250723102030-Fh6RT to apply the changes
    > Run mod log runs add . logs.zip --last-run to aggregate run logs

MOD SUCCEEDED in 1m 21s

info

Some of the repositories may show (no LST) and return the message Skipped recipe run because no LST was found. This could be because we failed to download the LST from Moderne or because the LST failed to build locally.

For the purposes of this tutorial, we will ignore this message and not worry about the repositories that don't have LSTs.

To learn more about what changed, you can command/ctrl click on the Fix results links generated in the above command. If you open one of these patch files up, you'll see that various dependencies in pom.xml or build.gradle files have been updated. While these updates to the dependencies are useful, they are only a minor part of what this recipe does. In the next section we'll take a look at the real power of this recipe – the data table that is produced.

Study the results of a recipe

If you've been following along, you'll know that we just ran the DependencyVulnerabilityCheck recipe. Let's take another look at the What to do next section produced at the end of the recipe run:

⏺ What to do next
    > A repository's source code doesn't match its LST. Run mod build to update the LSTs.
    > Click on one of the patch links above to view the changes on a particular repository
    > Run mod study to examine the following data tables produced by this recipe:
          > mod study . --last-recipe-run --data-table VulnerabilityReport
          > mod study . --last-recipe-run --data-table MavenMetadataFailures
          > mod study . --last-recipe-run --data-table RecipeRunStats
          > mod study . --last-recipe-run --data-table SourcesFileResults
    > Run npm install -g diff2html-cli to produce patch files on subsequent runs that are easier to view
    > Run mod git checkout . -b refactor/DependencyVulnerabilityCheck --last-recipe-run to prepare a refactor/DependencyVulnerabilityCheck branch for applying the changes
    > Run mod git apply . --last-recipe-run to apply the changes
    > Run mod git apply . --recipe-run 20250723102030-Fh6RT to apply the changes
    > Run mod log runs add . logs.zip --last-run to aggregate run logs

You may notice that one of the suggestions on what to do next is the mod study command. This command allows you to examine the data tables produced by the recipe run. Data tables are columnar data in a schema defined by the recipe.

In the above example, you'll see there are four data tables produced by this recipe:

• VulnerabilityReport
• MavenMetadataFailures
• RecipeRunStats
• SourcesFileResults

The VulnerabilityReport contains detailed information about the vulnerabilities that exist in the repositories. For instance, it will tell you what CVE a particular repository is affected by, what the current version is, what the minimum fixed version is, a clear summary of what is wrong, and how many levels deep the dependency is.

Let's generate this data table by running the following command:

mod study . --last-recipe-run --data-table VulnerabilityReport

You should see output similar to the following.

Moderne CLI 3.44.4

⏺ Reading organization

Found 1 organization containing 12 repositories (1s)
Found recipe run 20250723102030-Fh6RT


⏺ Building CSV output for each organization

▶ Default
    ✓ Data table produced
Done (1s)

⏺ Converting to Excel for each organization

▶ Default
    ✓ Added 214 rows
    ✓ Data table produced
Done (3s)

Data tables for each organization with rows are linked above

MOD SUCCEEDED in 4s

info

We used the short name for the data table (VulnerabilityReport) rather than the fully-qualified name. As long as the short name is distinct, you can do this to save some typing.

Open up the Excel file that is produced. You will see that the recipe found hundreds of vulnerabilities. You can sort them by severity to see what the most important ones to start with are – or you could find the ones that can be fixed with a version update only to quickly address some of the problems. Having a table like this can help you and your organization track and prioritize security issues.

Adjust the format of data tables

Maybe you don't really want an Excel spreadsheet as the output, though. Fortunately, the Moderne CLI lets you customize what you get out of data tables with templates. Let's run a new recipe to demonstrate this. Let's run a recipe to find all locations where the java.util.List add(..) method is used (For more information on how to select a particular method, check out our method patterns documentation).

Note: Please make sure to pick the org.openrewrite.java.search.FindMethods recipe when you run the following command as multiple recipes with this title may exist.

mod run . --recipe FindMethods -PmethodPattern="java.util.List add(..)"

# Select the following recipe: 
#   * Find method usages (org.openrewrite.java.search.FindMethods)

Once that's done running, we could run a similar study command as before to get an Excel file that contains detailed information about all of the places this specific method was found. Let's say, however, that you don't care about all of the columns and that you'd like a markdown file to be produced instead of an Excel spreadsheet.

We can filter the data table to only a couple columns we are interested in and then use a GoTemplate to produce a markdown file containing code samples for all of the matching methods we found:

mod study . --last-recipe-run --data-table MethodCalls --json sourceFile,method --template '{{"# Search results\n\n"}}{{range .}}{{"* "}}{{.sourceFile}}{{"\n```\n"}}{{.method}}{{"\n```\n"}}{{end}}' > methods.md

As you can see, the output is extremely flexible to meet whatever needs you have.

Commit changes and/or create PRs

So far, everything we've done has remained local to your machine. In a real-world situation, though, you'd definitely want to commit the results, test the changes, and open a PR in each repository. Let's walk through how to do this.

To begin, make sure you're still in the $HOME/workshop directory with the Default organization cloned. Then, run the following recipe to resolve common static analysis issues in all of the repositories:

mod run . --recipe CommonStaticAnalysis

You should see output similar to the following.

Moderne CLI 3.44.4

⏺ Reading organization

Found 1 organization containing 12 repositories (1s)

⏺ Running recipe org.openrewrite.staticanalysis.CommonStaticAnalysis

Run log

▶ aws/amazon-documentdb-jdbc-driver@develop (no LST)
    Skipped recipe run because no LST was found
▶ openrewrite/rewrite-recipe-bom@main
    ✓ Fix results
    ✓ Recipe run complete
▶ Netflix/ribbon@master
    ✓ Fix results
    ✓ Recipe run complete
▶ spring-projects/spring-petclinic@main
    ✓ Fix results
    ✓ Recipe run complete
▶ finos/spring-bot@spring-bot-master
    ✓ Fix results
    ✓ Recipe run complete
▶ finos/symphony-wdk@master
    ✓ Fix results
    ✓ Recipe run complete
▶ finos/messageml-utils@main
    ✓ Fix results
    ✓ Recipe run complete
▶ Netflix/photon@master
    ⚠ The latest LST is not up to date
    ✓ Fix results
    ✓ Recipe run complete
▶ awslabs/aws-saas-boost@main
    ✓ Fix results
    ✓ Recipe run complete
▶ apache/maven-doxia@master
    ✓ Fix results
    ✓ Recipe run complete
▶ spring-projects/spring-data-commons@main
    ✓ Fix results
    ✓ Recipe run complete
▶ finos/symphony-bdk-java@main
    ✓ Fix results
    ✓ Recipe run complete
Done (44s)

24m 7s saved by using previously built LSTs
182h 40m saved by using recipes

Produced results for 11 repositories.

⏺ What to do next
    > A repository's source code doesn't match its LST. Run mod build to update the LSTs.
    > Click on one of the patch links above to view the changes on a particular repository
    > Run mod study to examine the following data tables produced by this recipe:
          > mod study . --last-recipe-run --data-table RecipeRunStats
          > mod study . --last-recipe-run --data-table SourcesFileResults
    > Run npm install -g diff2html-cli to produce patch files on subsequent runs that are easier to view
    > Run mod git checkout . -b refactor/CommonStaticAnalysis --last-recipe-run to prepare a refactor/CommonStaticAnalysis branch for applying the changes
    > Run mod git apply . --last-recipe-run to apply the changes
    > Run mod git apply . --recipe-run 20250723102607-DvrxN to apply the changes
    > Run mod log runs add . logs.zip --last-run to aggregate run logs

MOD SUCCEEDED in 45s

Right now, if you cd to any of the repositories in the workshop directory, you won't see any of these changes. While you could apply these changes to the branches you have checked out, it's generally preferable to make changes inside of a branch and then submit a PR for said branch.

To begin, let's create a branch in each repository that has changes by running the following command:

mod git checkout . -b workshop-changes --last-recipe-run

You should see output similar to the following.

Moderne CLI 3.44.4

⏺ Reading organization

Found 1 organization containing 12 repositories (1s)
Found recipe run 20250723102607-DvrxN


⏺ Executing git checkout

Command output will be written to log

▶ apache/maven-doxia@master
    ✓ Switched to branch workshop-changes
▶ aws/amazon-documentdb-jdbc-driver@develop
    Skipped because there are no results to commit
▶ awslabs/aws-saas-boost@main
    ✓ Switched to branch workshop-changes
▶ finos/messageml-utils@main
    ✓ Switched to branch workshop-changes
▶ finos/spring-bot@spring-bot-master
    ✓ Switched to branch workshop-changes
▶ finos/symphony-bdk-java@main
    ✓ Switched to branch workshop-changes
▶ finos/symphony-wdk@master
    ✓ Switched to branch workshop-changes
▶ Netflix/photon@master
    ✓ Switched to branch workshop-changes
▶ Netflix/ribbon@master
    ✓ Switched to branch workshop-changes
▶ openrewrite/rewrite-recipe-bom@main
    ✓ Switched to branch workshop-changes
▶ spring-projects/spring-data-commons@main
    ✓ Switched to branch workshop-changes
▶ spring-projects/spring-petclinic@main
    ✓ Switched to branch workshop-changes
Done (1s)

Checked out 11 repositories.

⏺ What to do next
    > Commit your changes using mod git commit . -m "commit message" io.moderne.cli.commands.RecipeRun$Selected@3e9aac24.

MOD SUCCEEDED in 1s

Next, let's apply the changes from the recipe to these branches:

mod git apply . --last-recipe-run

If you cd into the project directories and run git status, you will see that you have a bunch of uncommitted and unstaged changes. Normally this would be where you would run tests and confirm that everything still works. For the purposes of the workshop, though, let's just pretend everything worked perfectly and move to the next step of staging the files and committing the changes.

To add the files to the list that should be committed, run the following command:

mod git add . --last-recipe-run

Then, to commit these changes, run the following command:

mod git commit . -m "Test common static analysis changes" --last-recipe-run

warning

Right now, GPG signing is not supported by the mod git commit command. If you use GPG signing, you'll either need to disable that temporarily or manually commit the changes in each repository without using the CLI.

Normally, the next step you would do would be to push the commit to a branch and open a PR for it. However, as we don't own these repositories and as we don't want to clutter them, please refrain from running the following commands against the repositories above.

There are a variety of ways to create PRs based on your goals. We'll provide a few of the most common examples below.

You could push commits to the repositories via:

# Please don't run this command during the workshop
mod git push . --last-recipe-run

warning

Depending on the branch you've checked out, you may need to specify an upstream branch when running mod git push such as in:

mod git push . --last-recipe-run --set-upstream <MigrationBranchName>

Or you could create a PR directly with the GitHub command line:

# Please don't run this command during the workshop
mod exec . --last-recipe-run -- gh pr create --title "refactor: Apply AssertJ best practices"

Or you could create PRs while filtering to only certain repositories, branches, origins, recipe runs, etc.:

mod git push . --recipe-run <id> --repository-branch main

Additional information

If you want to learn more about the Moderne CLI, we'd encourage you to check out the follow docs:

• Learn more about how to configure the CLI to meet your needs
• Learn more about how JDK selection works and how you might configure other locations for JDKs
• Learn how to use the Moderne IntelliJ plugin in combination with the CLI to test recipes

Or watch the following videos:

Differences between the Moderne CLI and the OpenRewrite build plugins

The OpenRewrite build plugins are designed to run a single recipe on a single repository at a time. When you run a recipe using these plugins, a new LST is produced regardless of whether or not the code for that repository has changed. This LST is temporarily stored in memory and used by the recipe before being discarded at the end of the recipe run. For large projects, this can be problematic as the entire LST must fit in memory for the recipe to work.

In contrast, the Moderne CLI is designed for scale. You can run recipes against multiple repositories at once and the LST does not need to fit into memory. This is because the Moderne CLI uses proprietary code to build the LST up in parts and then serializes/writes it to the disk (as part of the mod build command). Likewise, the mod run command will read this LST from the disk in pieces as it runs recipes rather than building the LST every time.

When running the Moderne CLI commands for the first time, you might notice that running a single recipe on a single repository is slower than the OpenRewrite build plugins. This is due to the fact that the OpenRewrite build plugins do not serialize the LST and write it to disk.

However, if you wanted to run more recipes against the same LST, you would see that the Moderne CLI drastically increases in speed compared to the OpenRewrite build plugins as the Moderne CLI can read the pre-built LST and execute recipes against it rather than having to build it again each time. Furthermore, if you wanted to, you could use the Moderne CLI to run a recipe against many repositories at once – which the OpenRewrite build plugins can't do.