4 ms·

There are a plethora of reasons not to put sales data into github issues. I appreciate the idea of reducing complexity. Focusing things around issue tracking gi

by erhk 5y ago

There are a plethora of reasons not to put sales data into github issues. I appreciate the idea of reducing complexity. Focusing things around issue tracking gives a good workflow for opening and closing, and also provids a finite goal, but theres often needs which cannot be met. I also dont think that its necessary to point out but I would not advise handing over all business organizing to github as a platform.

wereHamster 5y ago
> handing over all business organizing to github as a platform. GitHub is not the only issue tracker. Git itself is the easiest to migrate off of GitHub, issues is probably close next.
mlosgoodat 5y ago
> There are a plethora of reasons not to put sales data into github issues. Thanks for the details. Anecdotally; the author of the blog post and work environments I’ve been in did just that and … reality still exists. Me thinks personal opinions on how to store data are … personal opinions.
simonw 5y ago
Is your concern that GitHub employees might access your confidential sales data if it's in issues in a private repository? Because if you're worried about that, there's probably a whole bunch of even worse things that they could be doing with access to your source code, secrets and CI infrastructure.