Repository navigation
chore: regenerate update-journal-entry docs for in-step flow re-tags - #255
Merged
Merged
Conversation
The line_flows description now says the other side follows only when its lines were in step with the named ones; a line tagged differently on purpose keeps its tag. Docstring text only, no symbol or shape change.
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.
Regenerated from the server after the journal-entry re-tag fix (RoboFinSystems/robosystems
0116f0661). Theline_flowsdescription onupdate-journal-entrynow says the other side of the entry follows only when its lines were in step with the named ones; a line tagged differently on purpose keeps its tag.Docstring text only: no symbol, type or shape change. Rides a client patch.
🤖 Generated with Claude Code