nushell / nushell/nushell.github.io

Most frequently used Nushell commands chapter

Abierto
#899 27 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Lenguaje dominante
TypeScript
Estrellas
258
Forks
561
Merge medio
3 h 20 min
PR fusionados (30 d)
15

Descripción

UPD: for those who are interested result are published here:
https://github.com/maxim-uvarov/nu-commands-frequency-stats/blob/main/aggregated_stats/aggregated-freq-stats20230911.csv

Work on the script is in progress


Guys, I think it would be cool to add a chapter to the book about the most frequently used Nushell commands to help newcomers prioritize their learning efforts.

To gather statistics from several nushell users, I wrote this script.

After running this script, it will produce two files: a CSV with the commands and their frequency that were used in your history for more than 10 times and a YAML-formatted txt file with some additional information (as github doesn't allow to upload files with YAML extension into the comments).

Please feel free to alter that data by either increasing the frequency threshold included in the CSV report commands or by not attaching the YAML.txt file if you believe it could somehow harm your privacy.

If you would like to contribute your data, please run the script and upload your files in this thread so we could aggregate the data from them.

The script will ask you if you want to include stats only about built-in commands or all the commands that you used. It is up to you how much information you want to share.

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Línea de trabajo

Comienza revisando el script vinculado history-stats2.nu y los resultados publicados aggregated-freq-stats20230911.csv, y después inspecciona la estructura de capítulos existente del libro. Se considera terminado cuando se haya añadido un capítulo orientado a quienes se incorporan al proyecto, que utilice los datos de frecuencia de comandos recopilados y encaje con el estilo de documentación del libro.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
shell
Área
cli, documentation
Tipo de issue
Documentación
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
35/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.