Live
GPU‑Accelerated Inference on AWS Lambda via Managed InstancesClaude Code’s “Don’t Ask Again” local file leaks credentials to public reposPost‑training RL with PivotRL lifts Nemotron 3 Ultra coding benchmarkIntegrating AI Coding Agents into Development Workflows: Protocols, Practices, and Security ImplicationsAWS Quick’s new Meta ads AI connector: what engineers need to knowAI router data leakage forces engineers to rethink prompt pipelinesRust’s Agent Client Protocol simplifies AI‑agent integration for production workloadsUsing Gaussian Sharpening with Cloudflare Images: Practical Guidance for EngineersGPU‑Accelerated Inference on AWS Lambda via Managed InstancesClaude Code’s “Don’t Ask Again” local file leaks credentials to public reposPost‑training RL with PivotRL lifts Nemotron 3 Ultra coding benchmarkIntegrating AI Coding Agents into Development Workflows: Protocols, Practices, and Security ImplicationsAWS Quick’s new Meta ads AI connector: what engineers need to knowAI router data leakage forces engineers to rethink prompt pipelinesRust’s Agent Client Protocol simplifies AI‑agent integration for production workloadsUsing Gaussian Sharpening with Cloudflare Images: Practical Guidance for Engineers
GitHub

Multiple GitHub Accounts per Host Now Supported in Desktop 3.7

AI SummaryPowered by AI

GitHub Desktop 3.7 lets users add an unlimited number of accounts for the same host and bind each repository to a specific account. This change helps engineers, SREs, and security teams avoid credential mix‑ups and simplifies automation across personal, team, and service identities.

GitHub Desktop version 3.7 introduces the ability to sign in with more than one account on a single host—GitHub.com, GitHub Enterprise Server, or GHE.com—and to associate each local repository with the appropriate account. For practitioners who juggle personal, project, and service identities, the feature removes the need to constantly log out and back in, reducing friction in day‑to‑day development and deployment workflows.

What Changed in GitHub Desktop

The new release removes the previous one‑account‑per‑host limitation. Users can now add an unrestricted number of accounts via Settings → Options → Accounts. When cloning or publishing a repository, Desktop presents an account picker if multiple signed‑in accounts have access, or it selects the sole viable account automatically. Existing repositories are migrated to the account that was already in use, so single‑account setups remain unaffected.

Operational Impact for CI/CD and Automation

Automation pipelines that rely on Desktop‑generated credentials can now target a specific account without manual credential swaps. Practitioners should verify that the repository’s account association matches the identity used by their CI runners or deployment scripts. The ability to change the association from the repository settings or context menu means that credential updates can be performed locally without altering remote configuration.

  • When adding a new repository, select the intended account to ensure the correct SSH key or token is stored.
  • Review the account binding in the repository list to avoid accidental pushes from the wrong identity.
  • Use the account picker during cloning to keep automation scripts deterministic.

Security and Credential Management Considerations

Having multiple accounts on the same host expands the attack surface only if credentials are not managed carefully. Each account retains its own authentication tokens, so practitioners should treat them as separate secrets. Auditing which account is linked to a repository becomes a new operational checkpoint; mismatched bindings could lead to unauthorized pushes or exposure of service‑level tokens.

Because the migration of existing repositories is automatic, there is no immediate risk of credential loss, but teams should still confirm that the expected account appears in the repository settings after upgrade.

Related CloudNinjas coverage: DevOps.

What This Means For Practitioners

Adopt the new version, add the required accounts, and immediately audit repository‑account bindings to ensure they align with your access policies. Incorporate a verification step in onboarding scripts to confirm the correct account is selected when cloning or publishing. Finally, monitor token usage per account to detect any unexpected activity that could indicate credential misuse.

Originally published atGitHub Changelog