update Versioning of Graph Changes guide - #247
Merged
rpietzsch merged 1 commit intoAug 24, 2026
Merged
Conversation
The setup steps could not be followed anymore. Step 2 told users to add the Versioning Graph property while editing the graph, but that field is no longer part of the default form — it has to be added through the Add data menu first. Step 1 still described setting a Type in a dropdown instead of choosing the dedicated New Versioning Graph entry in the Add new graph dialog. - document the Add data step and the two-step create-graph wizard - describe the Versioning tab and the Latest Changesets table, both undocumented - replace the 20.10/24.1 screenshots with fresh ones taken on v26.2 - show screenshots inline instead of inside collapsible admonitions - move Setup before Usage, since Usage depends on it Verified against CMEM v26.2.0: SPARQL UPDATE writes stay untracked, and the Versioning Graph property is only offered on void:Dataset graphs.
Test Results0 tests 0 ✅ 0s ⏱️ Results for commit e434ee9. ♻️ This comment has been updated with latest results. |
rpietzsch
deleted the
feature/Update-Versioning-of-Graph-Changes-CMEM-7587
branch
August 24, 2026 11:20
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
2 participants
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.
The setup steps could not be followed anymore. Step 2 told users to add the Versioning Graph property while editing the graph, but that field is no longer part of the default form — it has to be added through the Add data menu first. Step 1 still described setting a Type in a dropdown instead of choosing the dedicated New Versioning Graph entry in the Add new graph dialog.
Verified against CMEM v26.2.0: SPARQL UPDATE writes stay untracked, and the Versioning Graph property is only offered on void:Dataset graphs.