[FEATURE] Combine related sys_history entries on save - #128
Open
Kanti wants to merge 1 commit into
Open
Conversation
Kanti
changed the title
sys_history entries on save
Kanti
force-pushed
the
feature/auto-combine-sys_history-entries-on-save
branch
2 times, most recently
from
August 12, 2026 13:34
76ca515 to
cdc579e
Compare
Kanti
marked this pull request as ready for review
August 12, 2026 13:39
Merge consecutive record updates into a single history entry so editors see the effective change instead of intermediate save states. Changes that result in no effective difference are removed from the history. related #124
Kanti
force-pushed
the
feature/auto-combine-sys_history-entries-on-save
branch
from
August 12, 2026 14:08
cdc579e to
f78852f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Merge consecutive record updates into a single history entry so editors see the effective change instead of intermediate save states.
Changes that result in no effective difference are removed from the history.
related #124