DataKitchen DataOps Documention

Kitchen History

Git Handling

DataKitchen contents (Recipes) adhere to git version control as a product of a distinct, foundational git branch underpinning each Kitchen. Each Kitchen's History displays the history of git commits associated with its git branch.

Updates are Commits

DataKitchen refers to commits as updates. This is both to simplify terminology for non-technical users, and also because updates include levels of DataKitchen Recipe validations that using git directly does not support.

For the sake of clarity for non-technical users, DataKitchen commits are called updates.

Summary View

The Kitchen History summary provides a longitudinal view of a Kitchen's update history, with the latest update appearing first. The summary view delineates the history based on date. Each entry also includes the username of the update author and an update message.

Filter by Update Author

See the updates applied across Recipes in a Kitchen for a specified user.

See the updates applied across Recipes in a Kitchen for a specified user.

Search Update Messages

Filter a Kitchen's history searching across update messages.

Filter a Kitchen's history searching across update messages.

Detail View

Click on any individual update from the summary view to review that update's details. Each update detail view contains:

  • A default or custom change message
  • The datetime of the update
  • An update ID
  • An indication of the file(s) included
  • Highlighted changes

Deep-Linked Update History

Each update's detail view is located at a unique URL, facilitating collaboration across teams working to build a Recipe-Variation assembly line.

Updated 8 months ago


Kitchen History


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.