Kitchen History

Each kitchen has a Git branch to store recipes and maintain version control. The kitchen History page displays the branch commits and provides a centralized view of a kitchen's complete update history. The page is sorted chronologically, with the most recent updates first.

Every entry includes a summary of the changes, the username of the update author, timings, and an update message, if provided.

Note

Updates are commits. Automation commits are called updates because they include data that is not supported when using Git directly. For example, when you update a recipe, the system validates your work and commits the update to Git if no issues are detected.

View the kitchen History page

1. From the Kitchens page, select any kitchen.
2. Select HISTORY from the green menu.
3. On the kitchen History page, review the updates.
4. Use filters to narrow the list.
   • Commit Author: Select from this drop-down list to display only updates made by a specific user.
   • Message search: Enter keywords to find specific change messages.
5. Click on an update entry to view the details of the changes.

Tip

DKCloudCommand option: Use the kitchen-history command in the command line interface.

Commit Details view

Select any entry on the kitchen History page, to see the details of the changes that were made in the commit. Each update contains the following information:

• A default or user-entered change description.
• The date and time of the update.
• An update ID.
• A list of the files included and the changes made in the file (i.e. additions and deletions).
• Highlighted changes.

Share commit details

To facilitate collaboration across teams working to build a complete recipe-variation process, each Commit Details page is located at a unique URL. You can copy the URL and send this link to others with access to Automation.

Visual example in Automation

The Commit Details show information about a change in a kitchen's history.