github / github/app

[Requests and ideas] I’d like to share feedback about using the agent-merge skill on Windows.

Aperta
#1,270 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub
Bugs Requests and ideas
Lingua principale
Nessun dato sulla lingua
Stelle
2.1k
Fork
153
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

**Mood:** 😔
**Category:** Requests and ideas

I’d like to share feedback about using the agent-merge skill on Windows.

The overall workflow works, but setup and execution were not smooth compared to macOS/Linux. I hit multiple environment-specific issues before the script could run successfully:

The script assumes bash, gh, and jq are readily available in the same shell environment, which was not true on Windows.
Running via the default bash entry did not reliably expose gh.
Running via Git Bash introduced path-conversion issues for GitHub API endpoints (for example, leading /repos/... paths were rewritten as local filesystem paths).
jq was not available by default in the shell used by the script, and had to be installed and manually added to PATH.
I had to set MSYS_NO_PATHCONV=1 to prevent endpoint/path mangling.
After these fixes, the script worked, but the out-of-box experience on Windows is fragile.

Suggestions to improve Windows compatibility:

Add a Windows-specific preflight check in check-merge-conditions.sh for bash, gh, and jq.
Document the recommended shell explicitly (for example, Git Bash) and required environment variables.
Detect and guard against MSYS path conversion issues (or set MSYS_NO_PATHCONV=1 in-script when safe).
Improve error messages so users can quickly identify whether the failure is tool availability, path conversion, or API/auth related.
This would make agent-merge much more reliable and user-friendly on Windows.

---
| Field | Value |
| --- | --- |
| App version | 1.0.3 |
| OS | Windows 10.0.26200 |
| Theme | Tokyo Night |
| Path | /chat |
| Tenure | Week 6 |

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

Start by reading check-merge-conditions.sh and tracing how it invokes bash, gh, jq, and Git Bash on Windows. Verify the reported PATH and MSYS path-conversion cases first. Done means Windows users receive clear preflight or error guidance and the recommended shell and environment setup are documented.

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

Valutazione

Stack tecnologico
bash, github
Ambito
cli, operating-systems, tooling
Tipo di issue
Funzionalità
Difficoltà
3/5
Tempo stimato
1-2 giorni
Stato di attività
Tranquilla
Chiarezza
Abbastanza chiara
Idoneità per principianti
55/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.