Makefile.test for running your test executables

Generic drop in Makefile. GitHub Gist: instantly share code, notes, and snippets.

A developer's machine accumulates tools fast. A Rust CLI you compiled last year, a Python formatter installed via `uv`, a language server pulled from npm, a terminal emulator from a curl script, a Go binary built from source. Each came from a different package manager, each with its own install incantation you half-remember. I wanted a way to declare what I need without adopting a complex system like Nix or Ansible just for a single laptop. The result was a plain old Makefile. I wrote a short post on using Make (along with a tiny bash script and fzf) to create a searchable, single-command…

I know this could be considered blasphemous, but I constantly find myself using Make as a task runner. I have written my own task runner in the past, but somehow I always end up using make. I went, and I put together 3 quality of life snippets I use all the time and put it in a single makext.mk file that can be included in other Makefiles and wrote a basic readme for it. This is not meant to be a replacement for other task runners, but I do think it can be useful to some of you. https://github.com/mitjafelicijan/makext Check it out and see if it makes sense to you. Thanks…

Justfiles are like Makefiles, except Just is a command runner, whereas Make is a build system. As I understand it, Just was built to be a less arcane version of Make for collecting commands common to a code repository. When I first learned about Just, I realized that parsing arguments and running commands is exactly what shell scripts do, and there probably isn't much Just does that sh doesn't. This project proves that hypothesis by compiling Justfiles to portable (POSIX-compatible) shell scripts. just.sh is particularly useful for running Justfiles in esoteric environments where Just may…

`makedown` allows you to organise your shell scripts in one or several markdown files, by mix and matching different scripting languages for various commands and needs. zsh/bash/sh, python, javascript or anything else available on your system. Handy for replacing one-line-based package.json scripts or shell-based Makefiles. One can also write documentation and explanations to various commands in the same `.md` file. Most editors highlight correctly most languages in the markdown code blocks, even when you use several scripting languages. Here is a demo .md file…

Creating code samples in simple terminal interface