tldr
[column]
ui = auto
[branch]
sort = -committerdate
[tag]
sort = version:refname
[init]
defaultBranch = main
[diff]
algorithm = histogram
colorMoved = plain
mnemonicPrefix = true
renames = true
[push]
default = simple
autoSetupRemote = true
followTags = true
[fetch]
prune = true
pruneTags = true
all = true
# why the hell not?
[help]
autocorrect = prompt
[commit]
verbose = true
[rerere]
enabled = true
autoupdate = true
[core]
excludesfile = ~/.gitignore
[rebase]
autoSquash = true
autoStash = true
updateRefs = true
# a matter of taste (uncomment if you dare)
[core]
# fsmonitor = true
# untrackedCache = true
[merge]
# (just 'diff3' if git version < 2.3)
# conflictstyle = zdiff3
[pull]
# rebase = true
Four Reasons Why English Should Not be the Official Language of the United States: Statement Against White House Executive Order “Designating English as the Official Language of The United States”
A Fast, Innovator Friendly, and Community Driven Python Web Framework
Robyn merges Python's async capabilities with a Rust runtime for reliable, scalable web solutions. Experience quick project scaffolding, enjoyable usage, and robust plugin support.
Yaak is an offline and Git friendly app for HTTP, GraphQL, WebSockets, SSE, and gRPC.
Europäische Alternativen für digitale Produkte
Wir helfen Ihnen bei der Suche nach europäischen Alternativen für digitale Dienstleistungen und Produkte, wie Cloud-Dienste und SaaS-Produkte.
Turn Mastodon into your feed reader
Cascade layers recently [end of 2024] reached the completely arbitrary “baseline widely available” milestone, which means they have been available across all modern browsers for more than 30 months now.
I’ve been a huge advocate of cascade layers since day one. I can’t imagine writing CSS without layers. So obviously I have a lot to say about layers. But today I want to focus only on one point (and it’s worth repeating): Your CSS reset should be placed inside a cascade layer.