Fix broken links
This commit is contained in:
Ornella
Родитель
c3500cd884
Коммит
df6e4bf478
|
|
@ -3,7 +3,7 @@ Order: 42
|
|||
TOCTitle: GitHub Pull Requests
|
||||
PageTitle: Introducing GitHub Pull Requests for Visual Studio Code
|
||||
MetaDescription: Introducing GitHub Pull Requests for Visual Studio Code
|
||||
MetaSocialImage: /assets/blogs/2018/010/8/github_pr_hero.png
|
||||
MetaSocialImage: /assets/blogs/2018/09/10/github_pr_hero.png
|
||||
Date: 2018-09-10
|
||||
ShortDescription: Introducing GitHub Pull Requests for Visual Studio Code
|
||||
Author: Kenneth Auchenberg
|
||||
|
|
|
|||
|
|
@ -16,7 +16,7 @@ One of my responsibilities as a developer on the Visual Studio Code team is to m
|
|||
|
||||
## Visual Studio Code Engineering
|
||||
|
||||
Like any other open-source project, we need to have the right tooling and capabilities to receive, triage, and address as many code contributions as possible. This rings especially true in the developer tools universe, in which end users are developers themselves: they are a passionate, hard-working, and very effective group. As of this blog post, we have [148 open PRs as well as 3,482 closed ones](https://github.com/microsoft/vscode/pulls), which sets an average of ~3 PRs/day given the 3-year project lifespan so far. It is important that we are well equipped for handling this scale of contributions, not only to keep the project development healthy but also to help give other open-source projects an example of how to operate at this scale. Part of how we do this is by streamlining our workflow by [bringing the PR experience into the editor](/blogs/2018/010/8/introducing-github-pullrequests), but CI is the other important part of handling contributions at scale.
|
||||
Like any other open-source project, we need to have the right tooling and capabilities to receive, triage, and address as many code contributions as possible. This rings especially true in the developer tools universe, in which end users are developers themselves: they are a passionate, hard-working, and very effective group. As of this blog post, we have [148 open PRs as well as 3,482 closed ones](https://github.com/microsoft/vscode/pulls), which sets an average of ~3 PRs/day given the 3-year project lifespan so far. It is important that we are well equipped for handling this scale of contributions, not only to keep the project development healthy but also to help give other open-source projects an example of how to operate at this scale. Part of how we do this is by streamlining our workflow by [bringing the PR experience into the editor](/blogs/2018/09/10/introducing-github-pullrequests), but CI is the other important part of handling contributions at scale.
|
||||
|
||||
Up until very recently, we relied on the OSS community's default choices for public continuous integration: [Travis CI](https://travis-ci.org/) for our Linux and macOS builds and [AppVeyor](https://www.appveyor.com/) for Windows. Additionally, we used [Coveralls](https://coveralls.io/) to provide detailed test coverage reports. These services provide quality reports for PRs and code branches on our public repository, as they automate [compilation](https://github.com/microsoft/vscode/blob/master/build/lib/compilation.ts), run [code hygiene checks](https://github.com/microsoft/vscode/blob/master/build/gulpfile.hygiene.js) and [execute several test](https://github.com/microsoft/vscode/tree/master/test) suites, all of which is essential in order to maintain quality in a distributed team with lots of incoming contributions. This combination of services requires the understanding and maintenance of at least 3 different systems, each with its own special file formats, syntax, quirks, limitations, etc.
|
||||
|
||||
|
|
|
|||
|
|
@ -13,7 +13,7 @@ December 4, 2018 Jonathan Carter, [@lostintangent](https://twitter.com/LostInTan
|
|||
|
||||
Pull requests are a critical collaboration tool for millions of developers every day, facilitating asynchronous code reviews and the distribution of knowledge amongst teams and open-source communities. Because of this widespread utility and adoption, any advancement to the PR review workflow can have a significant impact on developer productivity, product quality and release velocity.
|
||||
|
||||
In September, along with GitHub, [we announced the GitHub Pull Requests extension](https://code.visualstudio.com/blogs/2018/010/8/introducing-github-pullrequests), which enabled developers to review source code in the same place they write it: inside their familiar and highly-customized editor. Today, we're excited to share a sneak peek of a new experience that will further enhance in-editor PR reviews with support for **rich, multi-repository code navigations**.
|
||||
In September, along with GitHub, [we announced the GitHub Pull Requests extension](https://code.visualstudio.com/blogs/2018/09/10/introducing-github-pullrequests), which enabled developers to review source code in the same place they write it: inside their familiar and highly-customized editor. Today, we're excited to share a sneak peek of a new experience that will further enhance in-editor PR reviews with support for **rich, multi-repository code navigations**.
|
||||
|
||||
<iframe src="https://www.youtube.com/embed/DAqDEi0fGco?rel=0&disablekb=0&modestbranding=1&showinfo=0" frameborder="0" allowfullscreen></iframe>
|
||||
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ Order: 51
|
|||
TOCTitle: SSH Tips and Tricks
|
||||
PageTitle: Visual Studio Code Remote SSH Tips and Tricks
|
||||
MetaDescription: Visual Studio Code Remote-SSH Tips and Tricks
|
||||
MetaSocialImage: /assets/blogs/20110/8/03/social-remote-ssh.png
|
||||
MetaSocialImage: /assets/blogs/2019/10/03/social-remote-ssh.png
|
||||
Date: 2019-10-03
|
||||
ShortDescription: Remote SSH Tips and Tricks with Visual Studio Code
|
||||
Author: Sana Ajani
|
||||
|
|
|
|||
|
|
@ -3,7 +3,7 @@ Order: 52
|
|||
TOCTitle: Inspecting Containers
|
||||
PageTitle: Inspecting Docker Containers with Visual Studio Code
|
||||
MetaDescription: Inspecting Docker Containers with Visual Studio Code
|
||||
MetaSocialImage: /assets/blogs/20110/8/31/social-remote-containers.png
|
||||
MetaSocialImage: /assets/blogs/2019/10/31/social-remote-containers.png
|
||||
Date: 2019-10-31
|
||||
ShortDescription: Inspecting Docker Containers with Visual Studio Code
|
||||
Author: Bowden Kelly
|
||||
|
|
|
|||
|
|
@ -11,7 +11,7 @@ MetaSocialImage:
|
|||
|
||||
May 6, 2020 by Alex Ross, [@alexr00](https://github.com/alexr00/)
|
||||
|
||||
On the Visual Studio Code team, we use GitHub [issues](https://github.com/microsoft/vscode/issues) to track all of our work. From our detailed [iteration plans](https://github.com/microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Aiteration-plan) to individual bugs, we track everything as GitHub issues. Given how important issues are to our team and other GitHub projects, we wanted to add GitHub issues integration to VS Code. This addition complemented the GitHub Pull Request work we [announced](https://code.visualstudio.com/blogs/2018/010/8/introducing-github-pullrequests) over a year ago. Starting with VS Code version 1.45, this new support to move the issues and source code closer together will be available in the [GitHub Pull Requests and Issues](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github) extension (formerly named GitHub Pull Requests).
|
||||
On the Visual Studio Code team, we use GitHub [issues](https://github.com/microsoft/vscode/issues) to track all of our work. From our detailed [iteration plans](https://github.com/microsoft/vscode/issues?q=is%3Aopen+is%3Aissue+label%3Aiteration-plan) to individual bugs, we track everything as GitHub issues. Given how important issues are to our team and other GitHub projects, we wanted to add GitHub issues integration to VS Code. This addition complemented the GitHub Pull Request work we [announced](https://code.visualstudio.com/blogs/2018/09/10/introducing-github-pullrequests) over a year ago. Starting with VS Code version 1.45, this new support to move the issues and source code closer together will be available in the [GitHub Pull Requests and Issues](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github) extension (formerly named GitHub Pull Requests).
|
||||
|
||||
## Our integration approach
|
||||
|
||||
|
|
|
|||
|
|
@ -496,7 +496,7 @@ Key|Command|Command id
|
|||
|
||||
### GitHub Pull Request extension blog post
|
||||
|
||||
You can read Kenneth's recent [blog post](https://code.visualstudio.com/blogs/2018/010/8/introducing-github-pullrequests) announcing the new [GitHub Pull Request](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github) extension and discussing the collaboration between VS Code and the GitHub Editor team.
|
||||
You can read Kenneth's recent [blog post](https://code.visualstudio.com/blogs/2018/09/10/introducing-github-pullrequests) announcing the new [GitHub Pull Request](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github) extension and discussing the collaboration between VS Code and the GitHub Editor team.
|
||||
|
||||
### Using Azure Pipelines blog post
|
||||
|
||||
|
|
|
|||
|
|
@ -252,7 +252,7 @@ You can learn about new extension features and bug fixes in the [Remote Developm
|
|||
|
||||
You can also read two recent blog posts describing:
|
||||
|
||||
* [Remote SSH Tips and Tricks](https://code.visualstudio.com/blogs/20110/8/03/remote-ssh-tips-and-tricks)
|
||||
* [Remote SSH Tips and Tricks](https://code.visualstudio.com/blogs/2019/10/03/remote-ssh-tips-and-tricks)
|
||||
* [WSL 2 with Visual Studio Code](https://code.visualstudio.com/blogs/2019/09/03/wsl2).
|
||||
|
||||
## Preview features
|
||||
|
|
|
|||
|
|
@ -503,7 +503,7 @@ Feature highlights in 1.41 include:
|
|||
|
||||
You can learn about new extension features and bug fixes in the [Remote Development release notes](https://github.com/microsoft/vscode-docs/tree/master/remote-release-notes/v1_41.md).
|
||||
|
||||
You can also read a recent blog post about [Inspecting Containers with VS Code](https://code.visualstudio.com/blogs/20110/8/31/inspecting-containers) and try the updated [Using C++ and WSL in VS Code](https://code.visualstudio.com/docs/cpp/config-wsl) tutorial.
|
||||
You can also read a recent blog post about [Inspecting Containers with VS Code](https://code.visualstudio.com/blogs/2019/10/31/inspecting-containers) and try the updated [Using C++ and WSL in VS Code](https://code.visualstudio.com/docs/cpp/config-wsl) tutorial.
|
||||
|
||||
### ESLint
|
||||
|
||||
|
|
|
|||
|
|
@ -347,7 +347,7 @@ You can learn about new extension features and bug fixes in the [Remote Developm
|
|||
|
||||
### GitHub Pull Requests and Issues
|
||||
|
||||
Formerly named "GitHub Pull Requests", the [GitHub Pull Requests and Issues](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github) extension has been letting you manage and review pull requests from within VS Code for [over a year now](https://code.visualstudio.com/blogs/2018/010/8/introducing-github-pullrequests). Now, the extension as been expanded to include support for GitHub Issues.
|
||||
Formerly named "GitHub Pull Requests", the [GitHub Pull Requests and Issues](https://marketplace.visualstudio.com/items?itemName=GitHub.vscode-pull-request-github) extension has been letting you manage and review pull requests from within VS Code for [over a year now](https://code.visualstudio.com/blogs/2018/09/10/introducing-github-pullrequests). Now, the extension as been expanded to include support for GitHub Issues.
|
||||
|
||||
Issue support includes:
|
||||
|
||||
|
|
|
|||
Загрузка…
Ссылка в новой задаче