You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+13-9Lines changed: 13 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ In this topic, we'll cover:
15
15
## Process for contributing
16
16
17
17
**Step 1:** Open an issue describing the article you wish to write and how it relates to existing content.
18
-
The content inside the **docs** folder is organized into sections that are organized by content area (e.g., debugger). Try to determine the correct folder for your new content. Get feedback on your proposal.
18
+
The content inside the **docs** folder is organized into sections that are organized by content area (e.g., debugger). Try to determine the correct folder for your new content. Get feedback on your proposal.
19
19
20
20
You can skip this first step for small changes.
21
21
@@ -52,7 +52,7 @@ The Visual Studio team will review your PR and let you know if the change looks
52
52
53
53
The maintainers will merge your PR into the master branch once feedback has been applied and your change looks good.
54
54
55
-
On a certain cadence, we push all commits from master branch into the live branch and then you'll be able to see your contribution live at https://docs.microsoft.com/en-us/cpp/.
55
+
On a certain cadence, we push all commits from master branch into the live branch and then you'll be able to see your contribution live on [docs.microsoft.com](https://docs.microsoft.com/en-us/cpp/).
56
56
57
57
## DOs and DON'Ts
58
58
@@ -66,7 +66,7 @@ Below is a short list of guiding rules that you should keep in mind when you are
66
66
-**DO** blog and tweet (or whatever) about your contributions, frequently!
67
67
68
68
> [!NOTE]
69
-
> You might notice that some of the topics are not currently following all the guidelines specified here and on the [style guide](./styleguide/template.md) as well. We're working towards achieving consistency throughout the site. Check the list of [open issues](https://github.com/dotnet/docs/issues?q=is%3Aissue+is%3Aopen+label%3Aguidelines-adherence) we're currently tracking for that specific goal.
69
+
> You might notice that some of the topics are not currently following all the guidelines specified here and on the [style guide](./styleguide/template.md) as well. We're working towards achieving consistency throughout the site. Check the list of [open issues](https://github.com/MicrosoftDocs/cpp-docs/issues?q=is%3Aissue+is%3Aopen+label%3Aguidelines-adherence) we're currently tracking for that specific goal.
70
70
71
71
## Building the docs
72
72
@@ -82,14 +82,18 @@ If you are comfortable with other ways listed on the link above, feel free to us
82
82
83
83
You can build and preview the resulting site locally using a built-in web server. Navigate to the `cpp-docs\docs` folder on your machine and type the following command:
84
84
85
-
```
86
-
docfx -t default --serve
87
-
```
85
+
`docfx -t default --serve`
88
86
89
-
This starts the local preview on [localhost:8080](http://localhost:8080). You can then view the changes by going to `http://localhost:8080/[path]`, such as http://localhost:8080/cpp/visual-cpp-in-visual-studio.html.
87
+
This starts the local preview on [localhost:8080](http://localhost:8080). You can then view the changes by going to `http://localhost:8080/[path]`, such as `http://localhost:8080/cpp/visual-cpp-in-visual-studio.html`.
90
88
91
-
**Note:** the local preview currently doesn't contain any themes at the moment so the look and feel won't be the same as in the documentation site. We're working towards fixing that experience.
89
+
**Note:** the local preview currently doesn't contain any themes at the moment so the look and feel won't be the same as in the documentation site. We're working towards fixing that experience. We also use some custom extensions for embedded video, notes, and included documents, that won't be visible in the preview.
92
90
93
-
# Contributing to samples
91
+
##Contributing to samples
94
92
95
93
For now, include required sample code as inline code blocks in your article. The repo has a codesnippets folder, but this is not ready for public contributions.
94
+
95
+
## Contributor license agreement
96
+
97
+
You must sign the [Contribution License Agreement (CLA)](LICENSE) before your PR is merged. This is a one-time requirement for projects in docs.microsoft.com. You can read more about [Contribution License Agreements (CLA)](http://en.wikipedia.org/wiki/Contributor_License_Agreement) on Wikipedia.
98
+
99
+
You don't have to sign the agreement up-front. You can clone, fork, and submit your PR as usual. When your PR is created, it is classified by a CLA bot. If the change is trivial (for example, you fixed a typo), then the PR is labeled with cla-not-required. Otherwise, it's classified as cla-required. Once you signed the CLA, the current and all future pull requests are labeled as cla-signed.
Copy file name to clipboardExpand all lines: docs/assembler/inline/accessing-c-or-cpp-data-in-asm-blocks.md
+2-7Lines changed: 2 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,18 +2,13 @@
2
2
title: "Accessing C or C++ Data in __asm Blocks | Microsoft Docs"
3
3
ms.custom: ""
4
4
ms.date: "11/04/2016"
5
-
ms.reviewer: ""
6
-
ms.suite: ""
7
-
ms.technology: ["cpp-tools"]
8
-
ms.tgt_pltfrm: ""
9
-
ms.topic: "article"
5
+
ms.technology: ["cpp-masm"]
6
+
ms.topic: "conceptual"
10
7
dev_langs: ["C++"]
11
8
helpviewer_keywords: ["data members [C++], in __asm blocks", "data access [C++], in __asm blocks", "__asm keyword [C++], data members", "structure types in __asm blocks"]
0 commit comments