Jon Church jonchurch

Discussion Minutes

Felix (@feba66), Joel (@space-admiral), James (@Green), and Jon (@jonchurch) in attendance
What are goals of the Project?
2946 folks are in the discord
Joel is the main dev lead
Artokun is other dev and helping to manage the other devs
- 2 people have access to the codebase (artokun and Joel)
Felix has already been using real concepts he has learned for Spacetraders in his CompSci studies
The HTTP spec is a great compromise on technology because it is approachable for learners

I want to look at commit history, individual commits, the changes a commit brought, etc.

I don't know the exact commit or range I want.

To see X number of commits, pass a numerical flag: git log -3 will output the last 3 commits.

Further filter by author:

Some commits touch many files at once to do QoL or reformat code, with trivial diffs. These commits infamously muddy the output of git blame.

However, since git v2.23, git allows you to provide a list of commits to ignore in the blame. This feature is called "ignore revision(s)"

You can provide these commits in multiple ways:

the CLI flag --ignore-rev <commit>
the CLI flag --ignore-revs-file which accepts a file in fsck.skipList format (commits seperated by newlines, # prefixed comments allowed as of Git 2.20) NOTE: at time of writing (git v2.25.1) this flag will evaluate the path relative to your repo root, not your current working directory!

Enable git config feature.manyFiles true to opt in to a few settings to help speed up large repos. At time of writing it sets index.version=4 and core.untrackedCache=true
Run git gc to garbage collect unreachable objects, clean up reflog. Under the hood this runs git prune && git repack && git rerere
Do you have a slow startup time for new shell sessions? Many devs are using some prompt that shows git status in your prompt. After every command it will use git to check the status of your index. When git is slow in general, this will slow down your interactive shells. One quick solution is to disable that status check in your prompt. For zsh you can do that by running git config oh-my-zsh.hide-info true, add a --global flag if you want to set this option globally.

	/**
	* Reads the first 8 bytes (magic bytes) from the provided file.
	*
	* @param {File} file - The file from which the magic bytes are to be read.
	* @returns {Promise<Uint8Array>} A promise that resolves to a `Uint8Array` containing the first 8 bytes of the file.
	* @throws {Error} Throws an error if the file cannot be read or if there's another reading issue.
	*
	* @example
	* const file = new File(["content"], "filename.txt");
	* sniffMagicBytes(file).then(bytes => {

	#!/bin/sh
	# Called by "git commit" with no arguments. The hook should
	# exit with non-zero status after issuing an appropriate message if
	# it wants to abort the commit.
	#
	# Will skip linting if the commit is a merge commit
	# to avoid introducing formatting diffs on already committed code

	PATH=$PATH:/usr/local/bin:/usr/local/sbin
	echo --------------------------------------------

	import axios, { AxiosInstance, AxiosRequestConfig } from 'axios';

	interface Job {
	id: string;
	createdAt: string;
	status: 'queued' \| 'processing' \| 'completed' \| 'failed';
	priority?: number;
	retryCount?: number;
	data?: any;
	execute: () => void;

	{
	"data": [
	{
	"symbol": "COSMIC",
	"name": "Cosmic Engineers",
	"description": "The Cosmic Engineers are a group of highly advanced scientists and engineers who seek to terraform and colonize new worlds, pushing the boundaries of technology and exploration.",
	"headquarters": "X1-ZA40-15970B",
	"traits": [
	{
	"symbol": "INNOVATIVE",

	# input looks like
	# ~/proj/src/some/file/path.tsx(60,9): error jest/no-conditional-expect : Avoid calling `expect` conditionally`

	npm run lint -- --quiet \| awk 'BEGIN { FS="(" }; {print $1O}' \| uniq -u

	function copyBranch() {
	navigator.clipboard.writeText(
	document.querySelector('.pr-header-branches').children[0].textContent
	)
	}