What other ones should there be? Mediawise, seems like video-attachments are too rare to develop an inhouse viewer solution for. For binary types...why would they need to be viewed inline?
I was thinking of non-media files - arbitrary files. PDF, docx, odf, txt, etc. The lack of being able to attach arbitrary files to Issues is awkward. That said, for open projects, I can see them wanting to avoid becoming an accidental free file-hosting service.
Those would be useful but I guess in terms of issue-reporting, screenshots are universally valuable for showing erroneous program behavior...when would other filetypes be useful for that, except in cases of programs that are designed to output such filetypes (attaching an ODF would be useful for an ODF generator, for instance)?
Not just outputs, but also inputs. As a hypothetical example, if I had a project that processed MP3 files, and it had bugs on certain files, it would be nice to be able to attach the MP3 files that triggered the bugs to an issue.
Would it not be useful to have test cases covering the broken behaviour (making it not specific to the issue, but rather stuff you could add in a commit)?
We're talking about issues reporting here, if there's a bug with a file being able to include the file itself (by the original reporter or somebody else) is valuable.
That's not super obvious or convenient for new or casual users. You could make the same argument about images; Just make a new repository (or gist) and put an image in it, then link to it!
Since there are no organization private gists [1] you can't use that method for private repositories.
[1] A gist can only be "private" in the sense that it's not listed on the public gist page. No access control takes place once someone guesses the url. That's probably good enough for most uses, but not for all.
Only for applications that don't deal with binary data. The company I work for uses ODF, PDF, DOC and other formats regularly and the inability to attach those files to GitHub issues is a monumental PITA.
