What types of assets should be committed to source control?

The correct approach is to commit all code and items that cannot be regenerated to source control. These assets are critical because they represent unique configurations or customizations made to the Sitecore instance that would be time-consuming or impossible to recreate from scratch. For example, this includes custom code, templates, and specific Sitecore items that have been manually configured, as they are integral to the functioning and setup of the application.

In contrast, other options suggest practices that may lead to issues. Committing all re-generateable assets, such as compiled binaries or auto-generated content, is generally unnecessary and can clutter the repository. Configuration files, while important, should be part of a broader strategy that includes all non-regenerateable assets to ensure that the complete environment can be reconstructed. Finally, only the latest version of the assets would hinder the tracking of changes over time and could complicate version management, making it difficult to revert to previous states if necessary.

Thus, committing all code and items that cannot be regenerated ensures that critical parts of the project are preserved, allowing for better collaboration, version control, and project recovery if needed.