Using a Token2 based id_ed25519_sk_rk key, I found very helpful to configure a different `pushurl` in `.git/config`. This allows to pull via HTTPS w/o a hardware touch.

    [remote "origin"]
            url = https://github.com/freeCodeCamp/devdocs.git
            pushurl = git@github.com:freeCodeCamp/devdocs.git

GitHub dropped http authentication so this only works for public repos (not that the UX or security of http auth for git is nice).

Can git be configured to use different keys for push and pull? (You can obviously use different upstreams, but thats not as elegant.) Most git servers let you specify read vs read-write privileges (aka “deployment keys”) so you could use one key to pull updates that doesn’t need touch and another key to push (which does).

GitHub did not drop http auth. They prefer you use http instead of ssh.

What they dropped was auth using your account name and password. You need to use a token as your password or use an extra tool like their cli client to setup auth (but it sucks if you have multiple accounts).

You configure separate entries in your ssh conf.

    Host gh-auth
      Hostname github.com
      Identityfile blah
      User git

pushurl = gh-auth:freeCodeCamp/devdocs.git

Ruff's rule is derived from Pylint: https://docs.astral.sh/ruff/rules/unspecified-encoding/

A very tiny router is provided by nanostores: https://github.com/nanostores/router

Maybe not so much for an Internet Protocol router?

Video: https://youtu.be/U7pZbCnJxEw?t=6105 (Kernel Recipes 2025 - Day 2)

Very useful. For configparser.ConfigParser I've found https://stackoverflow.com/a/57307141

Nice, it has landed. Now I'm getting:

> warning: Could not set up terminal for $TERM 'xterm-ghostty'. Falling back to hardcoded xterm-256color values

How could this happen? We're storing deploy credentials in GitHub, and configure fully automated deploy pipelines using YAML and Shell. Escaping 101. xD

https://xkcd.com/1638/

They're self-hosting at https://gitlab.wikimedia.org/explore