Timeline for Link GitHub project to Code Review
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:40 | history | edited | CommunityBot |
replaced http://codereview.stackexchange.com/ with https://codereview.stackexchange.com/
|
|
| Jul 6, 2015 at 22:27 | vote | accept | Loki Astari | ||
| Jul 4, 2015 at 23:03 | history | edited | Simon Forsberg | CC BY-SA 3.0 |
added 568 characters in body
|
| Jul 2, 2015 at 11:56 | history | edited | Simon Forsberg | CC BY-SA 3.0 |
added 260 characters in body
|
| Jun 28, 2015 at 15:40 | comment | added | Loki Astari | I am the last person you should ask about designing something visual (back end C++ remember). I am just throwing out ideas (see if any resonate with meta users). | |
| Jun 28, 2015 at 12:02 | comment | added | Simon Forsberg | @LokiAstari If I will be the one to implement it, I will probably make it an option :) | |
| Jun 28, 2015 at 1:38 | comment | added | Loki Astari | While there is not an accepted answer we could go with one metric. Like: Being-Reviewed: <Answer Count>. When an answer is accepted it goes to Reviewed: <View Count>. | |
| Jun 28, 2015 at 1:26 | comment | added | Loki Astari | To me. The actual score is not that important. But "view_count" is a measure that people have at least looked at it. If there is an accepted answer should be included in some way. Maybe "answer_count". | |
| Jun 27, 2015 at 23:48 | history | answered | Simon Forsberg | CC BY-SA 3.0 |