Skip to content

CLI: enable `dry-run` to use @entry

E. Rivas requested to merge er433/docs/getting-started-with-entries into dev

Motivation and Context

The Getting started tutorial is not using entries.


In this MR we update the file to use @entry. It also fixes dry-run to use @entry correctly.


  • compiler
  • website
  • webide
  • vscode-plugin
  • debugger

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Performance improvement (non-breaking change that improves performance)
  • None (change with no changelog)


Additional fix: dry-run sub-command has been fixed to work with @entry in top-level.


  • Changes follow the existing coding style (use dune @fmt to check).
  • Tests for the changes have been added (for bug fixes / feature).
  • Documentation has been updated.
  • Changelog description has been added (if appropriate).
  • Start titles under ## Changelog section with #### (if appropriate).
  • There is no image or uploaded file in changelog
  • Examples in changed behaviour have been added to the changelog (for breaking change / feature).
Edited by E. Rivas

Merge request reports