The example contradicts itself in such a short blog post (the example creates and reads ~/artifacts.txt, the prose claims repeatedly artifacts are anything in ~/artifacts/).

This is also an even worse design than path artifacts in Gitlab CI.

▲

melezhik a day ago | parent [-]

Oh. It’s just a typo. Why it’s worse ?

▲

thenewnewguy a day ago | parent [-]

It's a typo that carried over to the second code example of trying to read the file too? Is the sample code completely untested?

	▲	melezhik a day ago \| parent [-]
		the example is fixed, thanks for spotting that