48 ms·
My productivity app is a Git repository (that happens to be a GitLab wiki git repository at $WORK as well) with my "priority queue" text file and the following
by rav 5y ago
My productivity app is a Git repository (that happens to be a GitLab wiki git repository at $WORK as well) with my "priority queue" text file and the following bash function. The contents of the text file are similar to what Jeff Huang describes in the blog post (but MUCH less organized). Since it's in version control, I can freely delete old content that's no longer relevant for my day-to-day, and then I frequently use git log -p to search for old text in the file if it becomes relevant. The bash command also pushes and pulls automatically, so it can be used across my devices.
plan-edit() {
cd ~/wiki &&
git diff --exit-code &&
vim Rav-priority-queue.txt &&
! git diff --quiet Rav-priority-queue.txt &&
git commit -qm 'Update Rav-priority-queue.txt' Rav-priority-queue.txt &&
git pull -q --rebase &&
git push -q
}
- dotancohen 5y agoWhy rebase? I would imaging that preserving history would be a feature. An important feature at that.
- dahart 5y agoThat rebase doesn’t lose any history, it’s just flattening the commit sequence coming from multiple computers. This is a good normal/default workflow for personal repos.
- dotancohen 5y agoI see, thanks.
- rav 5y agoAs dahart mentions in a sibling comment, the todo-list doesn't operate with branching - all edits are performed by one person according to the real-time circumstances. Any Git history divergence is a matter of technical accident and not an expression of feature branching/merging.
- _dain_ 5y agoI have something similar, a folder full of text files that gets automatically committed to a git repo. Each file is a note or todo list item. When I want to review or search through things I do `cat *.txt | less` or similar. When I finish an item I just delete the file and commit. That keeps it tidy while also keeping an archive of old items if I need it (in practice I rarely do).