Support for newlines in VSTS PRs
See original GitHub issueI have been creating PRs using the VSTS CLI and love how simple it is. However, one of the biggest problems for me is that there’s no way to include newlines in the --description
flag.
I’ve tried:
vsts pr create -s foo -t bar -d "Hello <br/> world"
vsts pr create -s foo -t bar -d "Hello \n world"
vsts pr create -s foo -t bar -d "Hello `n world"
all of which show up as plaintext in the VSTS PR rather than actual new lines. Here’s my (not great) workaround in VSTS:
then I host a markdown file somewhere which has a rich description.
Am I doing something wrong?
Issue Analytics
- State:
- Created 5 years ago
- Comments:14 (9 by maintainers)
Top Results From Across the Web
Create a pull request to review and merge code - Azure Repos
Visual Studio 2019 | Visual Studio 2022. Create pull requests (PRs) to change, review, and merge code in a Git repository.
Read more >Copying cope from PRs Files tab ignores line breaks
Hi team. I have a mac vsc and rider and when trying to copy code from the files tab on pull request, the...
Read more >Find and replace with a newline in Visual Studio Code
Since VS Code release 1.3, the regex find has supported newline characters. To use this feature set the find window to regex mode...
Read more >A Peek at Latest C# 11 Features Coming in November with ...
Visual Studio 2022 version 17.1: Generic attributes · Newlines in string interpolation expressions · List patterns. To try out the new features, ...
Read more >Find and replace with a newline in Visual Studio Code
In the local searchbox ( Ctrl + F ) you can insert newlines by pressing Ctrl + Enter . multiple-line-support.gif (Local searchbox).
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@Koubek See my comment on June 4th. This issue has been left open because we plan to address it.
Fixed in release 0.1.3