gistash, RFCs
Created:
What if we can use Github’s gist as we use git stash? I
initially thought of this as a way to “backup” drafts I’m working on
here. I start writing posts with a .txt extension that I
.gitignore, so that I don’t commit half finished posts to
git plus also my blog generation script
won’t pick up the .txt files for processing. It will be
nice to stash them away to a private gist.
The solution is a script to store given files in a github gist, update them in place if they already exist.
When creating a new gist:
$ gistash *.txt
uploading a.txt
uploading b.txt
done.When updating an existing, gist(say
28fe346dc83fd26a43c351c507c6599d) that you have permissions
to update:
$ gistash *.txt 28fe346dc83fd26a43c351c507c6599d
updating a.txt
updating b.txt
uploading c.txt
done.Gist has an API to update a gist which can be used to implment this.
Only thing remaining is to actually write the code ;). The little “write up”, is a nice segue to this article I read today:
Update 2024-03-21: I wrote the code - https://gist.github.com/btbytes/73d6ddb0cf940e730edf22a60208691b with the help of Anthropic.AI.
From around the web
Scaling Engineering Teams via Writing Things Down and Sharing - aka RFCs.
When you consider that some of the most robust software things were built using the RFC process, involving people working in different organizations, often with conflicting interests, using “written down” things to make engineering decisions is a great practice.