[repo-assist] Bump Fantomas to 7.0.6 and fix stale NuGet/login comment

Aperta Adatta ai principianti
#1,796 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
68/100
Tipo di issue
Refactoring
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
fsharp, github-actions

Direzione di ricerca

Aggiorna .config/dotnet-tools.json per usare Fantomas 7.0.6 e correggi il commento sulla versione di NuGet/login in .github/workflows/push-master.yml. Inizia esaminando le versioni attualmente bloccate, quindi esegui dotnet tool restore, CheckFormat e Build. Il lavoro è terminato quando la versione dello strumento e il commento corrispondono, la formattazione non segnala modifiche e la build ha esito positivo.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

agentic-workflows automation repo-assist

🤖 This PR was created by Repo Assist, an automated AI assistant.

Changes

  1. Fantomas 7.0.1 → 7.0.6 (.config/dotnet-tools.json): a safe patch-version bump of the code-formatting tool used by CheckFormat/Format build targets. Verified CheckFormat reports "No files need formatting" with the new version, so no source reformatting was required.
  2. Stale comment fix (.github/workflows/push-master.yml): a previous Dependabot PR bumped the pinned SHA for NuGet/login from v1.1.0 to v1.2.0, but left the adjacent # this hash is v1.1.0 comment unchanged. Updated the comment to correctly say v1.2.0 to avoid confusing future maintainers/dependabot reviewers.

Rationale

Both are low-risk engineering hygiene fixes: keeping tooling current and keeping in-repo documentation/comments accurate and in sync with actual pinned versions.

Trade-offs

None identified — Fantomas 7.0.6 is a patch release within the same major/minor line already in use, and the comment fix is purely documentation.

Test Status

  • dotnet tool restore: ✅ succeeded, Fantomas 7.0.6 installed
  • dotnet run --project build/build.fsproj -t CheckFormat: ✅ passed ("No files need formatting")
  • dotnet run --project build/build.fsproj -t Build: ✅ succeeded, 0 errors (pre-existing warnings only, unrelated to this change)
  • Full RunTests was not executed for this docs/tooling-only change since it does not affect runtime or test code; Build + CheckFormat cover the affected surface.

[!WARNING]
Protected Files — Push Permission Denied

This was originally intended as a pull request, but the patch modifies protected files. A human must create the pull request manually.

Protected files

The push was rejected because GitHub Actions does not have workflows permission to push these changes, and is never allowed to make such changes, or other authorization being used does not have this permission.

Create the pull request manually
# Download the patch from the workflow run
gh run download 33319289611 -n agent -D /tmp/agent-33319289611

# Create a new branch
git checkout -b repo-assist/eng-fantomas-nuget-login-comment-2026-08-30-477d89435e20f717 main

# Apply the patch (--3way handles cross-repo patches)
git am --3way /tmp/agent-33319289611/aw-repo-assist-eng-fantomas-nuget-login-comment-2026-08-30.patch

# Push the branch and create the pull request
git push origin repo-assist/eng-fantomas-nuget-login-comment-2026-08-30-477d89435e20f717
gh pr create --title '[repo-assist] Bump Fantomas to 7.0.6 and fix stale NuGet/login comment' --base main --head repo-assist/eng-fantomas-nuget-login-comment-2026-08-30-477d89435e20f717 --repo fsprojects/FSharp.Data

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@ae8d551f07c7ed7619f8c58c7bb4c3ac89395d38
Lingua principale
F#
Stelle
874
Fork
281
Merge medio
55m
PR unite (30g)
1

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di fsprojects/FSharp.Data

Tutte le issue di fsprojects/FSharp.Data

Issue simili

Altre issue su DevOps

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.