Local GitHub Config
With awesome tools like GitNub and GitX adding GitHub integration, it would be great if you didn’t have to keep re-entering you username and API token. So let’s settle on…
With awesome tools like GitNub and GitX adding GitHub integration, it would be great if you didn’t have to keep re-entering you username and API token.
So let’s settle on a standard, pioneered by GitNub:
$ git config --global github.user defunkt $ git config --global github.token 6ef8395fecf207165f1a82178ae1b984
(Remember to replace @defunkt@ and @6ef8395fecf207165f1a82178ae1b984@ with your own username and token.)
Applications and scripts can easily access this information:
$ git config --global github.user defunkt
You can also access ~/.gitconfig directly.
I just pushed out new versions of my gist script and the gist.el mode which use this method. Check the code for examples in Ruby and Emacs Lisp.
If you’re a developer, please adopt this method of storing GitHub data. Your users will thank you!
Written by
Related posts
What 986 million code pushes say about the developer workflow in 2025
Nearly a billion commits later, the way we ship code has changed for good. Here’s what the 2025 Octoverse data says about how devs really work now.
Introducing Agent HQ: Any agent, any way you work
At Universe 2025, GitHub’s next evolution introduces a single, unified workflow for developers to be able to orchestrate any agent, any time, anywhere.
Octoverse: A new developer joins GitHub every second as AI leads TypeScript to #1
In this year’s Octoverse, we uncover how AI, agents, and typed languages are driving the biggest shifts in software development in more than a decade.