Thank you for sharing. Even thou I have a lot fewer projects and majority of my work happens on the projects of clients - I managed to take away some useful ideas and tips. Specifically using "issue" as a place where everything gets tied together and combining all aspects of a feature into a single main-branch commit is something I will try to do more from now on.
Since your workflow is so GitHub centered, one place that IMO could use more structuring is GitHub issue labels [1] [2] [3]. Defaults are quite ad-hoc, with color not really representing anything. And setting up new default labels for new projects can be automated with command line scripts.
Thank you for sharing these resources. One of my first steps on a new project that I'll work with on an extended basis is to add new labels, and delete the ugly default ones I won't use. I've never made time to articulate my frustrations with the default labels, but these articles do a great job of identifying the issues, and proposing practical solutions.
I come from a background in education, and there's so much more to thinking through categorization and labeling systems than many people realize. The way we tag things has a significant impact on how we think about them. An efficient, well-thought-out tagging system leads us to work more efficiently without even knowing it. A technically correct but fundamentally weak tagging system can easily end up hurting the process, by hiding things that we assume would surface when needed.
Yeah I could definitely do a better job with my labels.
I usually add a "research" label and use it for issues where I'm researching if an idea is good or not, and I try to apply "bug" or "enhancement" to everything, but I'm not very structured about it. And I use random colors because I'm too lazy to standardize those across repos!
Since your workflow is so GitHub centered, one place that IMO could use more structuring is GitHub issue labels [1] [2] [3]. Defaults are quite ad-hoc, with color not really representing anything. And setting up new default labels for new projects can be automated with command line scripts.
[1] http://karolis.koncevicius.lt/posts/improving_github_issue_l...
[2] https://medium.com/@dave_lunny/sane-github-labels-c5d2e6004b...
[3] https://robinpowered.com/blog/best-practice-system-for-organ...