Eric's Patented Colo(u)r Code
Wot, spell "bolour" with a 'k'?"
I color-code a lot of my ToDo lists as an organizational tool, and then edit the hell out of my posts as my work progresses.
Colo(u)r coding usually (but not always) means:
Red: ToDo; not yet addressed.
Magenta: Work in progress.
Purple: Work saved locally; ready to submit.
Blue: Committed to GitHub.
Cyan: Pull request submitted; not updated on-site yet.
Green: Completely complete.
Gold: I looked into this and determined no changes needed to be made. This is hard to read. Sorry.
Sometimes I engage in "off-label" usage of the colors for meanings other than the above, in ways that make sense to me. Yeah. Sorry.
I'll try to add some notes to posts that need them if I need to publicly clarify.
Nota Bene: Back in the CHM days, there was no GitHub step to the process involved. On the old forum, I used blue for what's now purple. There could still be some lingering posts here from before I moved away from the old color-coding convention. In a perfect world, they'll get edited.
Edit, 2019-12-20:
My use of color coding is evolving... As I see it now, there are more potential stages to the pipeline than colors I've been using...
1. ToDo; not yet addressed.
2. Work in progress, not saved yet.
3. Saved, in dirty working directory.
4. Saved & stashed.
5. Staged for commit.
6. Committed to local repo, not pushed yet.
7. Pushed to GitHub, no PR yet.
8. Pull request opened; not updated on-site yet.
9. Completely complete.
So, this is leading to some inconsistent usage; I've not standardized on anything yet.
Edit, 2021-05-05:
Still evolving. Steps 2-7 fly past so quickly that there's little point in making that many edits to a post to row through a long list of colors. Work is rarely saved in a partially-completed state.
These days, I pretty much start at red for step 1, go green when opening a pull request, which will be merged before too long.
