Skip to content

Latest commit

 

History

History
66 lines (48 loc) · 1.91 KB

File metadata and controls

66 lines (48 loc) · 1.91 KB

GitHub CLI setup (this machine)

Completed initial wiring so Hermes can help with repos under monerostar.

What was installed

  • GitHub CLI (gh) v2.96.0
  • Location: %LOCALAPPDATA%\Programs\gh\bin\gh.exe (user-local zip install)
  • User PATH updated to include that bin folder
  • Note: winget install GitHub.cli can hang on MSI/UAC on this host — user-local zip avoided that

Auth

  • gh auth login (device/browser flow)
  • Account: monerostar
  • Protocol: HTTPS
  • Token stored in Windows keyring
  • Scopes observed: repo, read:org, gist
  • gh auth setup-git — git credential helper points at gh

Workflow scope (footgun we hit)

Pushing a branch that touches anything under .github/workflows/* requires the workflow scope. Without it, git push is rejected even though the rest of the branch pushes fine. It shows up as a push rejection, not a login error, which makes it easy to misread.

# check scopes quickly
gh auth status

# add the workflow scope (device/browser prompt)
gh auth refresh -s workflow

# confirm
gh auth status

Add the scope before you start editing workflows, so the push doesn't fail mid-PR. Note: a fresh device login can time out waiting for the browser on this host; run the refresh when you are at the keyboard.

Git identity

user.name  = monerostar
user.email = 203146215+monerostar@users.noreply.github.com

Noreply email keeps the address private; commits still attach to the GitHub user for contributions when pushed.

Smoke checks

gh auth status
gh repo list monerostar
gh api user --jq .login

Guardrails

  • No drive-by pushes or contribution farming
  • Prefer clear commits with short messages
  • Never commit .env, tokens, wallet addresses, or live Hermes profile data
  • Before pushing a branch that touches .github/workflows/*, confirm the workflow scope is present (gh auth status), or the push will be rejected