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
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -68,7 +68,7 @@ Some of this style guide is automated with GitHub Actions, but feel free to run
68
68
* Code blocks using the `batch` language tag automatically receive `$` prompt when rendered. To typeset a Bash code block without a prompt, use the `bash` language tag (e.g., \`\`\`batch CODE\`\`\`). The two use the same syntax highlighter, the only difference is the absence of the prompt.
69
69
* To display blocks of text without a language (e.g., output of a script), use \`\`\`text OUTPUT\`\`\`.
70
70
* To display error messages, use \`\`\`console ERROR MESSAGE\`\`\`.
71
-
* Quoted blocks (lines starting with `>`) are rendered as [a colored box](https://duckdb.org/docs/data/insert). The following box types are available: `Note` (default), `Warning`, `Tip`, `Bestpractice`, `Deprecated`.
71
+
* Quoted blocks (lines starting with `>`) are rendered as [colored boxed](https://duckdb.org/docs/stable/data/insert). The following box types are available: `Note` (default), `Warning`, `Tip`, `Bestpractice`, `Deprecated`.
72
72
* Always format SQL code, variable names, function names, etc. as code. For example, when talking about the `CREATE TABLE` statement, the keywords should be formatted as code.
73
73
* When presenting SQL statements, do not include the DuckDB prompt (`D `).
74
74
* SQL statements should end with a semicolon (`;`) to allow readers to quickly paste them into a SQL console.
@@ -155,8 +155,8 @@ Some of this style guide is automated with GitHub Actions, but feel free to run
155
155
156
156
## Preview, Stable and Versioned Pages
157
157
158
-
* The `preview` pages under <https://duckdb.org/docs/preview/> contains documentation for the latest preview (nightly) release of DuckDB. Most pull requests should target these pages. Pull requests documenting new features must target these pages.
159
-
* The `stable` pages under <https://duckdb.org/docs/stable/> contain documentation for the latest stable release of DuckDB (e.g., v1.2).
158
+
* The `preview` pages under <https://duckdb.org/docs/preview/> contains documentation for the latest preview (nightly) release of DuckDB.
159
+
* The `stable` pages under <https://duckdb.org/docs/stable/> contain documentation for the latest stable release of DuckDB (e.g., v1.2).**Most pull requests should target these pages.**
160
160
* The versioned pages (e.g., <https://duckdb.org/docs/v1.0/>) contain documentation for old stable versions of DuckDB. We generally only accept contributions to the latest stable version. Older pages are only maintained if they contain a critical error.
0 commit comments