GitHub Issues-only project management
blog.placemark.io
GitHub Issues-only project management
1–10 of 125 posts
Re: GitHub Issues-only project management
#2Wish you the best!
Re: GitHub Issues-only project management
#3Re: GitHub Issues-only project management
#4Re: GitHub Issues-only project management
#5Re: GitHub Issues-only project management
#6Having to create issues-only repositories seems like a sign that one may be using the wrong tool. But the simplicity of GitHub Issues, and the fact that most issues on my plate are related to a particular repo, makes it tempting.
Generically, we're talking "Kanban board" with swimlanes for the status, tags for categorization, and comments/attachments for discussion tracking.
I'm currently in a position to get some people sync'ed on projects for a client, and I am going to recommend we use Trello.
Kanban is just the right level of organization and visibility without going full agile-daily-standup-sprint overload.
Re: GitHub Issues-only project management
#7Re: GitHub Issues-only project management
#8> or the macOS “Sticky Notes” app that somehow still exists in 2021
Why isn’t Sticky Notes just a view into a particular folder in Notes.app, anyway?
Re: GitHub Issues-only project management
#9...In their ideal form, GitHub issues are homogenous. An issue is a task that you need to complete. If it isn’t a task, it isn’t an issue. If it’s done, it’s closed. If it’s not done, it’s open.
Re: GitHub Issues-only project management
#10Tangent, but: > or the macOS “Sticky Notes” app that somehow still exists in 2021 Why isn’t Sticky Notes just a view into a particular folder in Notes.app, anyway?