Fix newline escape characters in GitHub messages #84
Conversation
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
|
This PR doesn't work. |
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.
Description\n\nThis PR fixes the issue where text sent to GitHub via the gh CLI tool gets rendered with literal '\n\n' sequences in the GitHub issue text, rather than being properly formatted as newlines.\n\n## Changes\n\n- Added utility functions in to handle platform-specific newline escaping\n- Updated the system prompt to inform the AI about proper newline handling\n- Modified the shellStart tool to process GitHub CLI commands and properly escape newlines\n- Added tests for the new functionality\n\n## Testing\n\n- Added unit tests for the GitHub utility functions\n- Added a test for GitHub CLI command formatting in shellStart\n- Verified that all tests pass\n\nFixes #83