History contents
History shows applied generations from the current project's .admingen/history. Open it to check Generate times and affected files. Application-record changes are not included.
| Column | Meaning |
|---|---|
| Timestamp | Event time displayed in browser local time |
| Action | Recorded action |
| Changed files | Changed-file count |
| Operations | Plan-operation count |
| Generator | Generator version for this run |
Select 10, 25 or 50 entries per page. History entries shows the total.
When entries appear
Preview changes only displays a proposed result, so creates no applied-generation event. Applied generation with changes enters History. Multiple previews before Generate should not create multiple entries for one application.
No generation history yet means no entries. History unavailable is a read error, not proof of empty history. Dashboard also shows the latest entry in Last generation.
Practical example
Add Product.status, enable Filterable, inspect diff and Generate. History records time, version and changed-file count. Inspect current differences in Generate. Use version control for detailed source comparison and restoring older versions.
What History does not do
History cannot restore a selected generation or roll back the database. It does not audit user actions on articles/products/images. Ungenerated model edits can be cancelled through Discard ungenerated changes. Applied changes require source, migration and backup-aware recovery.
Generation results are also available through CLI. There is no separate CLI history command.