Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[repo-assist] [Repo Assist] Monthly Activity 2026-09

Abierto
  • ¿Algo no está bien?
#390 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

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

Línea de trabajo

Start by reviewing the linked pull requests, beginning with PR #386, and check the related issues #354 and #130 for context. Done means the listed PRs and comments have been reviewed or resolved and the monthly activity report no longer has outstanding actions.

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

Descripción

automation Documentation repo-assist

🤖 Repo Assist here — I'm an automated AI assistant for this repository.

Activity for September 2026

Suggested Actions for Maintainer

9 open Repo Assist PRs await review/merge. Maintainer note from 2026-04-07: "PRs look promising, some could be merged right away."

  • Review PR #386 (new, this run): fix: reorder open Plotly.NET before ipynb condition marker in docs (closes #354) — Review
  • Review PR #377: fix: remove CheckFunctionEpsilon from NelderMead stop criteria (closes #260) — Review
  • Review PR #376: feat: add Mann-Whitney U test (Wilcoxon rank-sum) — Review
  • Review PR #372: feat: Imputation.kNearestWeightedImpute for distance-weighted KNN (closes #318) — Review
  • Review PR #370: feat: expose QR decomposition with GramSchmidt/Householder (closes #317) — Review
  • Review PR #368: fix: ChiSquared.InvCDF scale parameter bug; InvCDF tests — Review
  • Review PR #367: feat: computeWithYates/computeWithWilliams chi-square corrections (closes part of #87) — Review
  • Review PR #365: feat: InvCDF for Beta, F, StudentT distributions (closes part of #262) — Review
  • Review PR #363: feat: InvCDF for Uniform, Exponential, Chi distributions (closes part of #262) — Review
  • Review PR #362: fix: ChiSquareTest.pearsonChiSquared for general r×c tables (closes #302, #344) — Review
  • Check comment on #354: Repo Assist diagnosed and fixed the docs eval bug — verify PR #386 addresses it fully — View
  • Check comment on #130: Repo Assist investigated FSI printer registration bug (assembly-boundary type matching hypothesis, workarounds suggested) — View

Future Work for Repo Assist

  • Continue issue scanning from #297 (Savitzky-Golay docs), #298 (tSNE), #299 (random forest), #309 (surface fitting — already has good maintainer answers in comments, may be closeable as answered)
  • Wilcoxon distribution implementation (#293, #213)
  • CUSUM implementation (#261)
  • Investigate community PRs #182 (Mann-Whitney-U, overlaps with our #376), #181 (X2contingency, overlaps with our #362), #179 (Dunn-Šidák, overlaps with our #374 which may have merged), #177 (Kolmogorov-Smirnov, WIP)

Run History

2026-09-28 08:49 UTC — Run
  • 🔧 Created PR #386: fix: reorder open Plotly.NET before ipynb condition marker in docs (closes #354)
  • 💬 Commented on #354: root-cause diagnosis and link to fix PR
  • 📁 Closed previous monthly activity issue #382 (May 2026) and opened this one

[!WARNING]

Firewall blocked 2 domains

The following domains were blocked by the firewall during workflow execution:

  • api.nuget.org
  • dc.services.visualstudio.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "api.nuget.org"
    - "dc.services.visualstudio.com"

See Network Configuration for more information.

Generated by 🌈 Repo Assist, see workflow run. Learn more.
Comment /repo-assist to run again

Add this agentic workflow to your repo

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/repo-assist.md@5d11aa2a05ce2c943c085acb7b12b583f83ed375
Lenguaje dominante
F#
Estrellas
228
Forks
58
Merge medio
2 d 7 h
PR fusionados (30 d)
1

Preparar el entorno

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.

Más de fslaborg/FSharp.Stats

Todos los issues de fslaborg/FSharp.Stats

Issues similares

Más issues de DevTools

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.