21–30 of 74 posts
I would love to hear why the github team waited so long to bring this feature into existence? I am sure there is a good reason (or maybe not) but it would be awesome if a member of the team would stop by and post the details.
Earlier quoted context omitted.
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)?
Earlier quoted context omitted.
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)?
Earlier quoted context omitted.
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)?
Core dumps and lengthy stacktraces spring to my mind.
I would love to hear why the github team waited so long to bring this feature into existence? I am sure there is a good reason (or maybe not) but it would be awesome if a member of the team would stop by and post the details.
We don't have roadmaps or a prioritized backlog, so we weren't exactly "waiting" to implement this. Someone got fed up with the image workflow, figured out a solution, grabbed some other people to help, and shipped it.
Earlier quoted context omitted.
We don't have roadmaps or a prioritized backlog, so we weren't exactly "waiting" to implement this. Someone got fed up with the image workflow, figured out a solution, grabbed some other people to help, and shipped it.
can you speak more to how this is built - even if its just at a high level?
Damn useful, I have to say. Thanks our friends :)
This is great. I was just complaining about this today in the other GH thread. What a nice surprise!
Heh, I was complaining about this in the other thread as well. It's encouraging to see some love for their issue tracker. Now if they could only fix their damn search! :)
http://searchco.de/?q=irq_create_mapping+url%3Agithub
Its not the full index of public repositories though as I don't have a hook into GitHubs project feeds like I do for Codeplex.
Earlier quoted context omitted.
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.