xxxigm 0a593f132c fix(skills/github): resolve .env via HERMES_HOME, not hardcoded ~/.hermes ... The GitHub skills' auth-detection fell back to reading GITHUB_TOKEN from a hardcoded ~/.hermes/.env. In the official Docker layout HERMES_HOME=/opt/data while tool subprocesses run with HOME=/opt/data/home, so `~/.hermes/.env` expands to /opt/data/home/.hermes/.env — a path that does not exist — while the real secrets file is /opt/data/.env. Result: the agent reports GITHUB_TOKEN as "not set" even though it is present and the dashboard Keys page shows it. Resolve the file as ${HERMES_HOME:-$HOME/.hermes}/.env (HERMES_HOME is bridged into tool subprocess env, falling back to ~/.hermes when unset) across all six auth-detection sites: github-auth (SKILL.md + scripts/gh-env.sh), github-issues, github-repo-management, github-pr-workflow, github-code-review.		2026-06-10 15:10:11 -07:00
..
templates	add github project management skill	2026-02-20 21:15:17 -08:00
SKILL.md	fix(skills/github): resolve .env via HERMES_HOME, not hardcoded ~/.hermes	2026-06-10 15:10:11 -07:00