-
-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keep track of recipe's changes #498
Comments
Would the comment be mandatory? I'd advise not to. |
Yes, but might help to explain why things have been done. Not always obvious. |
OK, can't wait to see your ticket asking to make it not-mandatory 😀 |
This issue has been automatically marked as stale because it has not had recent activity. It will be now be reviewed manually. Thank you for your contributions. |
A system working in a similar manner like the Gandi DNS zone revision system would be fine. |
This issue has been automatically marked as stale because it has not had recent activity. It will be now be reviewed manually. Thank you for your contributions. |
I think this ticket start to be really super urgent because:
We need IMO this very same feature on the CMS. In term of architecture I would:
|
This issue has been automatically marked as stale because it has not had recent activity. It will be now be reviewed manually. Thank you for your contributions. |
For the moment, we don't really keep track of changes on recipes (or this is not visible for end-users). We don't have any "audit trail". This has two major consequences:
It would be great to have a kind of revision log (like on Mediawiki).
Keeping track of each revision in json format and having a diff display between revisions would be really helpful.
I'm in favour as well to keep a big more information about each revision like:
The text was updated successfully, but these errors were encountered: