4 ms·
The author has some relevant blog posts (in GitHub issues) too: https://github.com/a327ex/blog/issues/35 https://github.com/a327ex/blog/issues/35 - BYTEPATH Po
by justinclift 6y ago
The author has some relevant blog posts (in GitHub issues) too:
https://github.com/a327ex/blog/issues/35 https://github.com/a327ex/blog/issues/35 - BYTEPATH Postmortem (2018)
https://github.com/a327ex/blog/issues/44 https://github.com/a327ex/blog/issues/44 - One Year Sales Data for BYTEPATH (2019)
- 65536 6y agoI was not aware that Steam had changed their policy on sharing sales data. That is great! Are there any other indie devs that have shared the data about their Steam sales in a similar fashion? Better yet, is there a good list of links gathered somewhere for that?
- siraben 6y agoThat's a very interesting way to use GitHub issues. I wonder what sort of problems can arise with vendor lock-in, though.
- cercatrova 6y agoIt's probably better to just make them Markdown inside the directory, you can export the Markdown files (since they're in git) but you can't export issues. Github renders both the same since, well, they're both Markdown.