Merge branch 'stdlib-js:develop' into feature/nanwmean

Author: SergeantQuickscoper

CONTRIBUTORS

@@ -78,6 +78,7 @@ Justyn Shelby <[email protected]>
 Karan Anand <[email protected]>
 Karthik Prakash <[email protected]>
 Kaushikgtm <[email protected]>
+Kavyansh-Bagdi <[email protected]>
 Kohantika Nath <[email protected]>
 Krishnam Agarwal <[email protected]>
 Krishnendu Das <[email protected]>
@@ -129,7 +130,9 @@ Rutam Kathale <[email protected]>
 Ruthwik Chikoti <[email protected]>
 Ryan Seal <[email protected]>
 Rylan Yang <[email protected]>
+SAHIL KUMAR <[email protected]>
 SHIVAM YADAV <[email protected]>
+Sahil Goyal <[email protected]>
 Sai Srikar Dumpeti <[email protected]>
 Sanchay Ketan Sinha <[email protected]>
 Sarthak Paandey <[email protected]>

docs/contributing/FAQ.md

@@ -27,7 +27,8 @@ limitations under the License.
 -   [How can I set up my development environment to contribute to stdlib?](#setup-dev-environment)
 -   [How can I install cppcheck?](#install-cppcheck)
 -   [I am seeing different return values in the JavaScript and C implementation for the same implementation.](#js-vs-c-return-values)
--   [What should I do if Markdown linting on my commits fails because my headings exceed the maximum permissible length?](#markdown-heading-length)
+-   [What should I do if linting on my commits fails because my headings or lines exceed the maximum permissible length?](#markdown-heading-length)
+-   [What should I do if JavaScript linting on my commits fails because my function exceeds the maximum permissible number of parameters?](#max-params)
 -   [I have opened a pull request, where can I seek feedback?](#pr-feedback)
 -   [I need to generate fixtures for my tests. How can I do that, and what are the best references for inspiration?](#generate-fixtures)
 -   [I am facing a `Shadowed declaration` linting error in my C files, how can I fix it?](#shadowed-declaration)
@@ -36,6 +37,7 @@ limitations under the License.
 -   [When should I use decimals in examples, benchmarks, and documentation, and when should I avoid them?](#decimal-usage)
 -   [How should I name my pull request?](#pr-naming)
 -   [How do I call the stdlib bot on my PR?](#stdlib-bot)
+-   [Why were many unrelated files automatically pushed to my PR when I committed my changes?](#auto-push)
 -   [Frequently used `make` commands](#freq-make-commands)
 -   [Other Links](#other-links)
 
@@ -45,7 +47,7 @@ limitations under the License.
 
 ## Introduction
 
-We appreciate your interest in contributing to stdlib! Below, we’ve compiled answers to some frequently asked questions (FAQs) from first-time contributors. If you’re new to the project or encounter any challenges, this guide is a great place to start.
+We appreciate your interest in contributing to stdlib! Below, we've compiled answers to some frequently asked questions (FAQs) from first-time contributors. If you're new to the project or encounter any challenges, this guide is a great place to start.
 
 <a name="first-time-contributor"></a>
 
@@ -64,8 +66,6 @@ There are primarily two options for setting up your development environment to c
 
 Note: The dev container does not yet support ARM64 architectures. For more information, or if you're interested in adding ARM64 support, you can visit this [issue][devcontainer-issue].
 
-TODO: Modify the dev container setup link to the exact file link once it is merged.
-
 <a name="install-cppcheck"></a>
 
 ## How can I install cppcheck?
@@ -101,15 +101,37 @@ If they pass, adjust the tolerance and add a note to the C tests indicating that
 
 <a name="markdown-heading-length"></a>
 
-## What should I do if Markdown linting on my commits fails because my headings exceed the maximum permissible length?
+## What should I do if linting on my commits fails because my headings or lines exceed the maximum permissible length?
+
+Consider whether the heading/line can be shortened by renaming variables (e.g., changing `strideX` to `sx`). If shortening is not possible, disable the lint rule at the top level using:
+
+- For JavaScript files:
+
+```javascript
+// eslint-disable-line max-len
+```
 
-Consider whether the heading can be shortened by renaming variables (e.g., changing `strideX` to `sx`). If shortening is not possible, disable the lint rule at the top level using:
+[Reference Comment][javascript-len-ref]
+
+- For Markdown files:
 
 ```markdown
 <!-- lint disable maximum-heading-length -->
 ```
 
-TODO: Can we add a reference PR link?
+[Reference Comment][markdown-len-ref]
+
+<a name="markdown-heading-length"></a>
+
+## What should I do if JavaScript linting on my commits fails because my function exceeds the maximum permissible number of parameters?
+
+Consider whether the number of parameters can be reduced. If reduction is not possible, disable the lint rule at the top level using:
+
+```javascript
+// eslint-disable-line max-params
+```
+
+[Reference Comment][javascript-params-ref]
 
 <a name="pr-feedback"></a>
 
@@ -269,6 +291,32 @@ Once you have created your PR, you can call the **stdlib-bot** to perform basic
 
 To see other available bot commands, comment `/stdlib help` on your PR.
 
+<a name="auto-push"></a>
+
+## Why were many unrelated files automatically pushed to my PR when I committed my changes?
+
+When you open a pull request or push changes to your feature branch, GitHub compares your feature branch against your `develop` branch and shows all the differences. If your feature branch contains outdated or extra changes, they will appear in the PR, even if they are unrelated to your work.
+
+To fix this, ensure that your feature branch is based on the latest `develop` branch. You can do this by updating your local `develop` branch and then merging it into your feature branch:
+
+```bash
+$ git checkout develop
+$ git pull upstream develop
+$ git push origin develop
+$ git checkout feature-branch
+$ git merge develop
+```
+
+After merging, push your changes to the remote repository:
+
+```bash
+$ git push origin feature-branch # git push also works
+```
+
+> **Note**: When developing stdlib, we recommend using `merge` instead of `rebase` once a PR is open. Rebasing rewrites your branch history, which usually requires a force-push to update the remote branch. This can disrupt other contributors who are reviewing or collaborating on your PR. Since stdlib uses squash and merge for PRs, we don't require a clean, linear commit history. Merge commits are acceptable as long as your diff only contains relevant changes. If you want to learn more about rebasing/merging, you can refer to our [Git guide][git-guide].
+
+Alternatively, you can call the **stdlib-bot** to merge changes from the `develop` branch into your PR. To do this, comment `/stdlib merge` on your PR.
+
 <a name="freq-make-commands"></a>
 
 ## Frequently used `make` commands
@@ -334,6 +382,7 @@ For more `make` commands, refer to the [documentation][benchmark] on running ben
 ## Other Links:
 
 - [Style Guide][style-guide]
+- [Git Cheatsheet][git-guide]
 - [Other make commands][make-commands]
 
 <section class="links">
@@ -346,6 +395,8 @@ For more `make` commands, refer to the [documentation][benchmark] on running ben
 
 [github-fork]: https://help.github.com/articles/fork-a-repo/
 
+[git-guide]: https://github.com/stdlib-js/stdlib/blob/develop/docs/contributing/git_cheatsheet.md#integration
+
 [development-guide]: https://github.com/stdlib-js/stdlib/blob/develop/docs/contributing/development.md
 
 [contributing-guide]: https://github.com/stdlib-js/stdlib/blob/develop/CONTRIBUTING.md
@@ -386,6 +437,12 @@ For more `make` commands, refer to the [documentation][benchmark] on running ben
 
 [make-commands]: https://github.com/stdlib-js/stdlib/tree/develop/tools/make/lib
 
+[markdown-len-ref]: https://github.com/stdlib-js/stdlib/blob/78e0cfd8b6c0429a443b07fd39fa9dd53bf44d23/lib/node_modules/%40stdlib/lapack/base/dgttrf/README.md?plain=1#L94
+
+[javascript-len-ref]: https://github.com/stdlib-js/stdlib/blob/78e0cfd8b6c0429a443b07fd39fa9dd53bf44d23/lib/node_modules/%40stdlib/lapack/base/dgttrf/lib/base.js#L111
+
+[javascript-params-ref]: https://github.com/stdlib-js/stdlib/blob/78e0cfd8b6c0429a443b07fd39fa9dd53bf44d23/lib/node_modules/%40stdlib/lapack/base/dgttrf/lib/base.js#L75
+
 </section>
 
 <!-- /.links -->