## Description
Fixes a few small typos in the developer documentation, and added new
lines in .md files for readability.
The changes are limited to typo and punctuation fixes. No grammar or
style rewrites are included. I am getting into contributing to open
source software and thought this might be a good start.
## User-facing changes (Release notes)
n/a
## Additional notes
Documentation-only typo cleanup.
This PR adds (partially complete) devdocs explaining how to make sure
PRs are properly formatted and labeled for the release notes.
## Release notes summary - What our users need to know
N/A
## Tasks after submitting
- [ ] Finish the HOWTO
- [ ] Add documentation on how to actually generate the release notes
(in nu_scripts/make_release)
#16455 had to restrict to `panic=abort` which breaks the error recovery
(and terminal raw mode disabling) on panic.
Mention this and the fact that loongarch64 are build by
https://github.com/nushell/nightly/releases
# Description
Adds a proper `ShellWarning` enum which has the same functionality as
`ParseWarning`.
Also moves the deprecation from #15806 into `ShellWarning::Deprecated`
with `ReportMode::FirstUse`, so that warning will only pop up once now.
# User-Facing Changes
Technically the change to the deprecation warning from #15806 is user
facing but it's really not worth listing in the changelog
<!--
if this PR closes one or more issues, you can automatically link the PR
with
them by using one of the [*linking
keywords*](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword),
e.g.
- this PR should close #xxxx
- fixes #xxxx
you can also mention related issues, PRs or discussions!
-->
# Description
<!--
Thank you for improving Nushell. Please, check our [contributing
guide](../CONTRIBUTING.md) and talk to the core team before making major
changes.
Description of your pull request goes here. **Provide examples and/or
screenshots** if your changes affect the user experience.
-->
I was interested in how nu-shell handles glibc, especially older
versions of it. I figured out from the docs that ubuntu 20.04 is
utilized. However, in reality, github has deprecated ubuntu 20.04, and
the code for ci.yaml in github workflow clearly states that it is 22.04.
This is just a minor doc update to clarify forgotten information
# Description
Removes the old `nu-cmd-dataframe` crate in favor of the polars plugin.
As such, this PR also removes the `dataframe` feature, related CI, and
full releases of nushell.
Time to expand our developer documentation, as some of this is still
tribal knowledge or things could otherwise slip through the cracks and
are costly to fix later.
This is still work in progress. But let's start somewhere.
Goal for this being in the repo is to make sure we update it more
frequently than the
https://github.com/nushell/nushell.github.io/tree/main/contributor-book
- Add folder for in-repo developer documentation
- Move PLATFORM_SUPPORT into devdocs
- Move our rust style to devdocs
- Use nushell code formatting in CONTRIBUTING
- Add FAQ file for developers with example questions
- Describe error handling best practices
Sylvestre Ledru