feat: add --description-file flag and warn on literal \n sequences#134
Closed
feat: add --description-file flag and warn on literal \n sequences#134
Conversation
schpetbot
force-pushed
the
schpetbot-pr-124d1fb1
branch
from
82ca955 to
91fc3f3
Compare
schpetbot
force-pushed
the
schpetbot-pr-124d1fb1
branch
from
91fc3f3 to
11826a8
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
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.
feat: add --description-file flag and warn on literal \n sequences
Fixes #133
Adds support for reading issue descriptions from files via
--description-file flag in both issue create and issue update commands.
Also adds detection and warning when descriptions contain literal
escaped newlines (\n as two characters) that won't render as line
breaks, providing guidance on proper multiline syntax.
Changes: