A static page generator for git.
Git repo: https://git.codemadness.org/stagit/
Onefetch is a command-line Git information tool written in Rust that displays project information and code statistics for a local Git repository directly on your terminal. The tool is completely offline - no network access is required.
By default, the repo's information is displayed alongside the dominant language's logo, but you can further configure onefetch to instead use an image - on supported terminals -, a text input or nothing at all.
It automatically detects open source licenses from texts and provides the user with valuable information like code distribution, pending changes, number of dependencies (by package manager), top contributors (by number of commits), size on disk, creation date, LOC (lines of code), etc.
Onefetch can be configured via command-line flags to display exactly what you want, the way you want it to: you can customize ASCII/Text formatting, disable info lines, ignore files & directories, output in multiple formats (Json, Yaml), etc.
As of now, onefetch supports more than 50 different programming languages; if your language of choice isn't supported: Open up an issue and support will be added.
A web-based text editor for networked note-taking, self-hostable on any Git repository. Retrieve knowledge as fast as you can type with zero-latency full-text search. Make serendipitous discovery via backlink traversal. Durable knowledge preservation with plaintext and Git backend. Efficient navigation and command powered by keyboard-centeric interaction design.
I don’t want this to be Vega’s Opinionated Big Ass Book To Give You An All-In-One Education, both because VegaOpBABTGYAAIOEdu is far less catchy, and because I don’t even think it’s possible. The more I write on this the more I value input of others and other resources I find, and the more happy I am that I called this project Opinionated Guides.
A Guide. That’s what I want this to be. I want OpGuides to be a resource that’s like your friend you can come back to for advice on where to go next, and I think that’s something the internet really needs. Search engines are were awesome for finding information, but only when you know what to look for, so I figure OpGuides can be a sort of curated information source, with the crappy results filtered out, the best resources I know of included, and a healthy mix of entertainment in the education so that it’s not a chore to read.
Edit your ~/.gitconfig file and add the following:
[alias]
pushall = !git remote | xargs -L1 -P0 git push --all --follow-tagsTo use it in a Git repository, git pushall after committing changes to your local copy.
Prefer using SSH over HTTP(S) for git.
In your ~/.gitconfig file:
[url "git@github.com:"]
insteadOf = http://github.com/
insteadOf = https://github.com/A shell script that lets you copy Git repos up to the IPFS network.
Convert the name of your main development branch from master to main with ease.
The tiniest PaaS you've ever seen. Piku allows you to do git push deployments to your own servers.
A hack that rewrites Git histories so you can spoof commit messages. Implemented as a shell script.
Don't be an asshole.
Git repositories of interest to tilde users.
gitin is a minimalist tool that lets you explore a git repository from command line. You can search from commits, inspect indvidual files and changes in the commits, see ahead/behind commits etc. It is an alternative and interactive way to explore the commit history. Also, you can explore your current state by investigating diffs, stage your changes and commit them.
Minimalistic git log based chat.
A minimalist decentralized issue management system based on Git. No back-end, no dependencies. Tickets are stored in the same Git repo as the project as text files in the .issues/ directory. Added to the other Git commands as an alias. Aims to be cross-platform, actually works on pretty much any *nix-alike.
A collection of things to do and try when Git gets fucked up. Named after NASA's in-flight crisis handbook.
Flight Rules are the hard-earned body of knowledge recorded in manuals that list, step-by-step, what to do if X occurs, and why. Essentially, they are extremely detailed, scenario-specific standard operating procedures.
Documents describing half-baked ideas and their kin.
Uses git's internal storage so no files are added in your project. As you would do with commits and branches, you can push your bugs to the same git remote you are already using to collaborate with other people.
Another self-hosted Github work-alike, forked from Gogs. Lightweight, written in Go, will run anywhere you can compile Go for. If you know how to use Github, you probably know how to use Gitea.
A Github workalike that is self-hosted. Written in Go, runs anywhere you can compile Go code for. Lightweight, will run happily on a RasPi. If you know how to use and admin Github, you know how to use Gogs already.
Github repo: https://github.com/gogs/gogs
How to set up a Git server on a CentOS box so that you can check code in and out of repositories across a network.