Adding nu version to scripts
Nobody has claimed this yet.
- Dominant language
- Nushell
- Stars
- 1.3k
- Forks
- 323
- Avg merge
- 3h 34m
- Merged PRs (30d)
- 4
Description
Hello, a recent commit (446f06f) broke the ssh custom completion for nu version 0.99.1 (the one shipped by dnf and fedora). This isn't a huge issue and I just downloaded the previous version.
However, it got me thinking, should the version of nu the script was developed for be commented in the script?
Ideally the script should display what versions of nu it works for, but this is unfeasible, probably.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing commit 446f06f and the affected SSH custom completion script to understand what changed for Nushell 0.99.1. Check how the repository currently records compatibility information; done would be an agreed, documented convention for identifying the Nushell version a script supports.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100