Using a self-rewriting README powered by GitHub Actions to track TILs
21–30 of 32 posts
Re: Using a self-rewriting README powered by GitHub Actions to track TILs
#22This is cool stuff. But could someone explain how this is a self-rewriting README? It looks to me like a file updated by a commit hook.
Re: Using a self-rewriting README powered by GitHub Actions to track TILs
#23The main difference is it provides full text search and global keyboard shortcuts so you can access it when you need it, without context switching.
Re: Using a self-rewriting README powered by GitHub Actions to track TILs
#24Here's my TIL implementation using Github Actions: https://github.com/mlpetersen/til
Mine is quite simple, you add new TIL's in the develop branch and commit them. Then it's built and added to the master branch.
Re: Using a self-rewriting README powered by GitHub Actions to track TILs
#25Re: Using a self-rewriting README powered by GitHub Actions to track TILs
#26My TIL for today is that I learnt what TIL stands for. How useless.
Re: Using a self-rewriting README powered by GitHub Actions to track TILs
#27Or is this trending on HN because it has the "GitHub Actions" buzzword in the title?
Edit: This is a serious question.
Re: Using a self-rewriting README powered by GitHub Actions to track TILs
#28Since when is programmatically generating a text file considered noteworthy / novel. Or is this trending on HN because it has the "GitHub Actions" buzzword in the title? Edit: This is a serious question.
It's the article I wish I had been able to read when I started working on this project.
Re: Using a self-rewriting README powered by GitHub Actions to track TILs
#29Re: Using a self-rewriting README powered by GitHub Actions to track TILs
#30Implementation details here: https://github.com/simonw/til/compare/95d99f5bb7206948257195...