3 ms·
We try to keep as much in the repo as possible. So raw assets, markdown documentation etc. It suffers from many of the same problems, but having it be in the s
by stepbeek 7y ago
We try to keep as much in the repo as possible. So raw assets, markdown documentation etc.
It suffers from many of the same problems, but having it be in the same directory/editor that I'm making a code change makes it more likely that I'll update.
- montroser 7y agoThat makes sense. Sometimes we still do that for more technical projects like backend services. But often it's a project manager or a designer or a researcher adding meeting notes, or recordings of usability testing sessions, etc, and at that point the repo seems less obvious a choice. As a dev, I still want easy/quick access to all of that (and I want to know and be reminded that it all exists in the first place), but the repo, and even the GitHub wiki for the repo both seem not quite right for this.