Added missing characteristics of causally upstream of or within and causally downstream of or within#2109
Merged
Conversation
Member
Author
|
Should this small change also be mentioned in the changelog and term tracker annotation? |
Contributor
|
Yes please. |
Member
Author
Done! |
madbkr
approved these changes
Sep 15, 2025
stap-m
approved these changes
Sep 25, 2025
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
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.
Summary of the discussion
As discussed in #2106, some characteristics of some RO properties weren't correctly imported:
causally upstream of or withinshould be defined as the inverse ofcausally downstream of or withinType of change (CHANGELOG.md)
Update
causally upstream of or withincausally downstream of or withincausally downstream of or withinWorkflow checklist
Automation
Closes #2106
PR-Assignee
term tracker annotationReviewer