This workshop is for anyone who has ever felt nervous using Git. We’ll help you face your fears with this ‘choose your own adventure’ style game, where you will use Git commands to make choices and solve puzzles. Enter the Haunted Forest, explore the mysteries that lie within and see if you can survive the night!
To play this game you will need access to the Git CLI. In general in this game git branches refer to locations, and commits refer to things that have happened in the past so the commit history of a branch will tell the story of what happened in a certain place. Files represent something in the environment that can be interacted with in some way e.g. a tree or a building.
To begin run the 'start_game' script.
Welcome to the world of Git. I hope this document will help to advance your understanding of this powerful content tracking system, and reveal a bit of the simplicity underlying it — however dizzying its array of options may seem from the outside.
A Git server without all of the features of Github, Gitlab, or whatever. It's just a server designed for use over SSH. Configured with its own Git repository. Repos created on demand with just a git push. SSH in and browse the text-mode control panel. View files. Access control built in.
SSH key auth.
It's in the AUR. Packaged for lots of different distros, too.
Dolt is a SQL database that you can fork, clone, branch, merge, push and pull just like a git repository. Connect to Dolt just like any MySQL database to run queries or update the data using SQL commands. Use the command line interface to import CSV files, commit your changes, push them to a remote, or merge your teammate's changes.
All the commands you know for Git work exactly the same for Dolt. Git versions files, Dolt versions tables. It's like Git and MySQL had a baby.
Dolt ships with a MySQL compatible database server built in.
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 file based wiki that uses markdown.
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.