"These are all the tests that have been executed.","including this one.","and this one.","oh and don't forget this one"
9
"rb-extension-pack"
10
"master"
11
"Bug123:Summary of Bug123","Bug321:Summary of Bug321"
12
"Commit c1891xasd"
13
"Mark Loyzer","Mark's group"
14
"[Resolved]Line too long(82 > 79 characters). by Issuer's Name","[Resolved]description of other issue. by Issuer's Name","[Unresolved]Nice print statements! Remember to clean then up when you're done. Issuer's Name"
151
"Test.jpg","Test.txt" // don't think this is needed..?
"[Review Request]Fix Issues raise by Review Bot","[Review Request]added master branch","[Review by Reviewer's Name]I think this is a sweet feature!","[Review by Reviewr's Name]Nice print statements! Remember to clean them up when you're done.","[Review by Reviewer's Name]Line too long (82 > 79 characters)"
Loading...
mike_conley:
Y'know, thinking about it right now, I don't think this is CSV... like, a CSV file is something that could / should map properly to a spreadsheet...
You mention this in your notes, but the many-comments (or bugs, or attachment links) is kind of opposing the way CSV generally works.
I think a better way of doing this might be to visualize it as being inserted in an Excel spreadsheet, and extrapolating the CSV format from that.
Can you create a spreadsheet, and toss this review request data into it and see how it looks? I imagine that's what folks are using these CSV files for anyways - for putting into spreadsheets. We might as well try to find a way of formatting it to look good.