When overriding a step, the default logic for that step will not be executed. Instead, the script you specify using override-* will run. In this script, the default logic for that step can be run with the craftctl default command.
For example, if you want to modify a file after pulling and before building, you can override the pull step, run the step using craftctl default, and change the sources.
Metadata, such as the version or title of a snap, can be dynamically set within an override-* script using the craftctl set <key>=<value> command.
Replace <key> with the name of the value you want to change and <value> with what you want to change it to.
The following keys are supported:
For example, if you want to set the version of a snap based on the git tags for a project, override the pull step with a script that first runs craftctl default before executing the craftctl set version assignment with the git command to retrieve the version information: