From c7e7b980f12df8f84d3dc03e20dd826e57baabc3 Mon Sep 17 00:00:00 2001 From: Antoine du Hamel Date: Mon, 29 Apr 2024 22:27:35 +0200 Subject: [PATCH 1/4] Update Makefile --- Makefile | 1 + 1 file changed, 1 insertion(+) diff --git a/Makefile b/Makefile index b7871bf2185..ad54bdb6ba1 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,7 @@ -include config.mk BUILDTYPE ?= Release + PYTHON ?= python3 DESTDIR ?= SIGN ?= From a6cbec65c07c29f4bb00d47252673f5d15197bbc Mon Sep 17 00:00:00 2001 From: Antoine du Hamel Date: Tue, 7 May 2024 18:11:58 +0300 Subject: [PATCH 2/4] test: commit from API Reviewed-by: No One --- test/README.md | 39 --------------------------------------- 1 file changed, 39 deletions(-) delete mode 100644 test/README.md diff --git a/test/README.md b/test/README.md deleted file mode 100644 index 8a006facc0b..00000000000 --- a/test/README.md +++ /dev/null @@ -1,39 +0,0 @@ -# Node.js Core Tests - -This directory contains code and data used to test the Node.js implementation. - -For a detailed guide on how to write tests in this -directory, see [the guide on writing tests](../doc/contributing/writing-tests.md). - -On how to run tests in this directory, see -[the contributing guide](../doc/contributing/pull-requests.md#step-6-test). - -For the tests to run on Windows, be sure to clone Node.js source code with the -`autocrlf` git config flag set to true. - -## Test Directories - -| Directory | Runs on CI | Purpose | -| ---------------- | ---------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| `abort` | Yes | Tests that use `--abort-on-uncaught-exception` and other situations where we want to test something but avoid generating a core file. | -| `addons` | Yes | Tests for [addon](https://nodejs.org/api/addons.html) functionality along with some tests that require an addon. | -| `async-hooks` | Yes | Tests for [async\_hooks](https://nodejs.org/api/async_hooks.html) functionality. | -| `benchmark` | Yes | Test minimal functionality of benchmarks. | -| `cctest` | Yes | C++ tests that are run as part of the build process. | -| `code-cache` | No | Tests for a Node.js binary compiled with V8 code cache. | -| `common` | | Common modules shared among many tests. [Documentation](./common/README.md) | -| `doctool` | Yes | Tests for the documentation generator. | -| `es-module` | Yes | Test ESM module loading. | -| `fixtures` | | Test fixtures used in various tests throughout the test suite. | -| `internet` | No | Tests that make real outbound network connections. Tests for networking related modules may also be present in other directories, but those tests do not make outbound connections. | -| `js-native-api` | Yes | Tests for Node.js-agnostic [Node-API](https://nodejs.org/api/n-api.html) functionality. | -| `known_issues` | Yes | Tests reproducing known issues within the system. All tests inside of this directory are expected to fail. If a test doesn't fail on certain platforms, those should be skipped via `known_issues.status`. | -| `message` | Yes | Tests for messages that are output for various conditions (`console.log`, error messages etc.) | -| `node-api` | Yes | Tests for Node.js-specific [Node-API](https://nodejs.org/api/n-api.html) functionality. | -| `parallel` | Yes | Various tests that are able to be run in parallel. | -| `pseudo-tty` | Yes | Tests that require stdin/stdout/stderr to be a TTY. | -| `pummel` | No | Various tests for various modules / system functionality operating under load. | -| `sequential` | Yes | Various tests that must not run in parallel. | -| `testpy` | | Test configuration utility used by various test suites. | -| `tick-processor` | No | Tests for the V8 tick processor integration. The tests are for the logic in `lib/internal/v8_prof_processor.js` and `lib/internal/v8_prof_polyfill.js`. The tests confirm that the profile processor packages the correct set of scripts from V8 and introduces the correct platform specific logic. | -| `v8-updates` | No | Tests for V8 performance integration. | From 5636de6365b3c2eb0649c1d051d941726131c2fb Mon Sep 17 00:00:00 2001 From: Antoine du Hamel Date: Tue, 7 May 2024 18:13:47 +0300 Subject: [PATCH 3/4] test: commit from API Reviewed-by: No One --- doc/README.md | 117 -------------------------------------------------- out.txt | 1 + 2 files changed, 1 insertion(+), 117 deletions(-) delete mode 100644 doc/README.md create mode 100644 out.txt diff --git a/doc/README.md b/doc/README.md deleted file mode 100644 index 3d8ad624683..00000000000 --- a/doc/README.md +++ /dev/null @@ -1,117 +0,0 @@ -# Documentation style guide - -This style guide helps us create organized and easy-to-read documentation. It -provides guidelines for organization, spelling, formatting, and more. - -These are guidelines rather than strict rules. Content is more important than -formatting. You do not need to learn the entire style guide before contributing -to documentation. Someone can always edit your material later to conform with -this guide. - -* Documentation is in markdown files with names formatted as - `lowercase-with-dashes.md`. - * Use an underscore in the filename only if the underscore is part of the - topic name (e.g., `child_process`). - * Some files, such as top-level markdown files, are exceptions. -* Documents should be word-wrapped at 80 characters. -* `.editorconfig` describes the preferred formatting. - * A [plugin][] is available for some editors to apply these rules. -* Check changes to documentation with `make test-doc -j` or `vcbuild test-doc`. -* [Use US spelling][]. -* [Use serial commas][]. -* Avoid first-person pronouns (_I_, _we_). - * Exception: _we recommend foo_ is preferable to _foo is recommended_. -* Use gender-neutral pronouns and gender-neutral plural nouns. - * OK: _they_, _their_, _them_, _folks_, _people_, _developers_ - * NOT OK: _his_, _hers_, _him_, _her_, _guys_, _dudes_ -* When combining wrapping elements (parentheses and quotes), place terminal - punctuation: - * Inside the wrapping element if the wrapping element contains a complete - clause. - * Outside of the wrapping element if the wrapping element contains only a - fragment of a clause. -* Documents must start with a level-one heading. -* Prefer affixing links (`[a link][]`) to inlining links - (`[a link](http://example.com)`). -* When documenting APIs, update the YAML comment associated with the API as - appropriate. This is especially true when introducing or deprecating an API. -* When documenting APIs, every function should have a usage example or - link to an example that uses the function. -* For code blocks: - * Use [language][]-aware fences. (\`\`\`js) - - * For the [info string][], use one of the following. - - | Meaning | Info string | - | ------------- | ------------ | - | Bash | `bash` | - | C | `c` | - | C++ | `cpp` | - | CoffeeScript | `coffee` | - | Diff | `diff` | - | HTTP | `http` | - | JavaScript | `js` | - | JSON | `json` | - | Markdown | `markdown` | - | Plaintext | `text` | - | Powershell | `powershell` | - | R | `r` | - | Shell Session | `console` | - - If one of your language-aware fences needs an info string that is not - already on this list, you may use `text` until the grammar gets added to - [`remark-preset-lint-node`][]. - - * Code need not be complete. Treat code blocks as an illustration or aid to - your point, not as complete running programs. If a complete running program - is necessary, include it as an asset in `assets/code-examples` and link to - it. -* When using underscores, asterisks, and backticks, please use - backslash-escaping: `\_`, `\*`, and ``\` ``. -* Constructors should use PascalCase. -* Instances should use camelCase. -* Denote methods with parentheses: `socket.end()` instead of `socket.end`. -* Function arguments or object properties should use the following format: - * ``* `name` {type|type2} Optional description. **Default:** `value`.`` - - * For example: \* `byteOffset` {integer} Index of first byte to expose. **Default:** `0`. - - * The `type` should refer to a Node.js type or a [JavaScript type][]. -* Function returns should use the following format: - * \* Returns: {type|type2} Optional description. - * E.g. \* Returns: {AsyncHook} A reference to `asyncHook`. -* Use official styling for capitalization in products and projects. - * OK: JavaScript, Google's V8 - - * NOT OK: Javascript, Google's v8 -* Use _Node.js_ and not _Node_, _NodeJS_, or similar variants. - - * When referring to the executable, _`node`_ is acceptable. -* [Be direct][]. - - - -* When referring to a version of Node.js in prose, use _Node.js_ and the version - number. Do not prefix the version number with _v_ in prose. This is to avoid - confusion about whether _v8_ refers to Node.js 8.x or the V8 JavaScript - engine. - - * OK: _Node.js 14.x_, _Node.js 14.3.1_ - * NOT OK: _Node.js v14_ -* [Use sentence-style capitalization for headings][]. - -See also API documentation structure overview in [doctools README][]. - -For topics not covered here, refer to the [Microsoft Writing Style Guide][]. - -[Be direct]: https://docs.microsoft.com/en-us/style-guide/word-choice/use-simple-words-concise-sentences -[Javascript type]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Grammar_and_types#Data_structures_and_types -[Microsoft Writing Style Guide]: https://docs.microsoft.com/en-us/style-guide/welcome/ -[Use US spelling]: https://docs.microsoft.com/en-us/style-guide/word-choice/use-us-spelling-avoid-non-english-words -[Use sentence-style capitalization for headings]: https://docs.microsoft.com/en-us/style-guide/scannable-content/headings#formatting-headings -[Use serial commas]: https://docs.microsoft.com/en-us/style-guide/punctuation/commas -[`remark-preset-lint-node`]: https://github.com/nodejs/remark-preset-lint-node -[doctools README]: ../tools/doc/README.md -[info string]: https://github.github.com/gfm/#info-string -[language]: https://github.com/highlightjs/highlight.js/blob/HEAD/SUPPORTED_LANGUAGES.md -[plugin]: https://editorconfig.org/#download diff --git a/out.txt b/out.txt new file mode 100644 index 00000000000..04d6f905945 --- /dev/null +++ b/out.txt @@ -0,0 +1 @@ +Test with file addition From dd13a7e3cd0d881977c5d9d1f3743413e0dc3838 Mon Sep 17 00:00:00 2001 From: Renovate Bot Date: Sat, 21 Dec 2024 07:50:35 +0000 Subject: [PATCH 4/4] Add renovate.json --- renovate.json | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 renovate.json diff --git a/renovate.json b/renovate.json new file mode 100644 index 00000000000..7190a60b642 --- /dev/null +++ b/renovate.json @@ -0,0 +1,3 @@ +{ + "$schema": "https://docs.renovatebot.com/renovate-schema.json" +}