GeezerVison is showing github.com — doc: update tags in adding-new-napi-api.md · nodejs/node@60de663
File tree
Expand file treeCollapse file tree
Open diff view settings
Expand file treeCollapse file tree
Open diff view settings
Collapse file
Copy file name to clipboardExpand all lines: doc/contributing/adding-new-napi-api.md +2-2Lines changed: 2 additions & 2 deletions - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
@@ -18,7 +18,7 @@ Node-API. |
18 | 18 | ABI compatibility with other versions of Node.js. |
19 | 19 | * New API **should** be agnostic towards the underlying JavaScript VM. |
20 | 20 | * New API PRs **must** have a corresponding documentation update. |
21 | | -* New API PRs **must** be tagged as **n-api**. |
| 21 | +* New API PRs **must** be tagged as **node-api**. |
22 | 22 | * There **must** be at least one test case showing how to use the API. |
23 | 23 | * There **should** be at least one test case per interesting use of the API. |
24 | 24 | * There **should** be a sample provided that operates in a realistic way |
@@ -38,7 +38,7 @@ Node-API. |
38 | 38 | * Experimental status exit criteria **must** involve at least the |
39 | 39 | following: |
40 | 40 | * A new PR **must** be opened in `nodejs/node` to remove experimental |
41 | | - status. This PR **must** be tagged as **n-api** and **semver-minor**. |
| 41 | + status. This PR **must** be tagged as **node-api** and **semver-minor**. |
42 | 42 | * Exiting an API from experimental **must** be signed off by the team. |
43 | 43 | * If a backport is merited, an API **must** have a down-level |
44 | 44 | implementation. |
|