Building an application:
Committing Use the slc build command to commit builds into a Git repository provides robust tracking and storage and . Doing this enables you to track and version product deployments. However, committing Doing this manually commits both build products and dependencies (
node_modules) to Git, pollutes source branches, creates massive Git commits, and huge churn on development branches and repositories.
In contrast, using
slc build --commit commits an exact replica of current branch source and build products onto a deployment branch. After the commit, the deployment branch tip shows as a merge of the deployment and source branches. This enables you to keep a complete history of deployment builds in Git, separate from development branches. You can push deployment branches to the same repository as the development branches if you wish.