Repository navigation
chore: reformat long openspec config line to fix YAML parse warning. Add instruction for verification scope - #5041
Merged
Conversation
Signed-off-by: Jesus Recio <jrecio@izertis.com>
…ropose Signed-off-by: Jesus Recio <jrecio@izertis.com>
jesmrec
marked this pull request as ready for review
October 30, 2026 12:27
Signed-off-by: Jesus Recio <jrecio@izertis.com>
jesmrec
force-pushed
the
fix/openspec_config_yaml_parse_error
branch
from
November 3, 2026 09:10
756176d to
ae1f847
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
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.
Content is now split up in many short lines with indentation, so the parser never sees one gigantic line. The resulting string value after parsing is identical but the parser processes it in small, well-formed chunks instead of one oversized plain line.
Now, the long string with a leading
>-that means:Added a new directive to prevent the problem in the future.
Add instruction to scope verifications in openspec tasks
Related Issues
App:
ReleaseNotesViewModel.ktcreating a newReleaseNote()with String resources (if required)QA