Matt Stein mattstein

Craft 3 plugins for better author experience

Annotated Notes: For admin notes with automatic timestamps.

Control Panel Body Classes: Add body classes to various Control Panel screens for easier styling (in combination with Control Panel CSS).

Control Panel CSS: To make style tweaks to the control panel. See web/cp.css for styles.

Control Panel Nav: Custom navigation menus for each user type, for easier navigation.

With GitHub Actions, a workflow can publish artifacts, typically logs or binaries. As of early 2020, the life time of an artifact is hard-coded to 90 days (this may change in the future). After 90 days, an artifact is automatically deleted. But, in the meantime, artifacts for a repository may accumulate and generate mega-bytes or even giga-bytes of data files.

It is unclear if there is a size limit for the total accumulated size of artifacts for a public repository. But GitHub cannot reasonably let multi-giga-bytes of artifacts data accumulate without doing anything. So, if your workflows regularly produce large artifacts (such as "nightly build" procedures for instance), it is wise to cleanup and delete older artifacts without waiting for the 90 days limit.

Using the Web page for the "Actions" of a repository, it is possible to browse old workflow runs and manually delete artifacts. But the procedure is slow and tedious. It is fine to delete one selected artifact. It is not for a regular cleanup. We need

	#!/bin/bash
	if [ "$EUID" -ne 0 ]
	then echo "Please run as root"
	exit
	fi

	apt-get install pkg-config libmagickwand-dev -y
	cd /tmp
	wget https://pecl.php.net/get/imagick-3.4.3.tgz
	tar xvzf imagick-3.4.3.tgz

	const { createHttpLink } = require('apollo-link-http');
	const fetch = require('node-fetch');
	const store = require('store');
	const sourceNodes = require('gatsby/dist/utils/source-nodes');
	require('dotenv').config();

	const craftGqlUrl = process.env.CRAFT_GQL_URL;
	const craftGqlToken = process.env.CRAFT_GQL_TOKEN;

	module.exports = {