Timeline for What are the guidelines for reviewing?
Current License: CC BY-SA 4.0
45 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 29 at 6:47 | history | edited | Sonic the Anonymous Hedgehog | CC BY-SA 4.0 |
added 164 characters in body
|
| May 10, 2023 at 1:03 | history | edited | Makyen | CC BY-SA 4.0 |
"by others" is correct, but not needed. Only the first "approve" bullet item is a sentence: Change it to have the same form as the rest of the "approve" bullet items & remove periods.
|
| May 9, 2023 at 21:40 | history | edited | CDR | CC BY-SA 4.0 |
added 1 character in body
|
| May 9, 2023 at 21:21 | history | edited | Makyen | CC BY-SA 4.0 |
Reorder Basic Workflow to go through the non-approve steps first, as those shouldn't be short-circuited for an approval. Be more explicit that reviewers should not approve Code of Conduct violations.
|
| Nov 2, 2022 at 19:20 | history | edited | starball | CC BY-SA 4.0 |
add reminder to flag NLN on comments that are addressed by an edit in a way that makes them NLN
|
| Feb 22, 2022 at 2:08 | history | edited | Sonic the Anonymous Hedgehog | CC BY-SA 4.0 |
added 232 characters in body
|
| Sep 22, 2021 at 23:43 | history | edited | Sonic the Anonymous Hedgehog | CC BY-SA 4.0 |
added 1586 characters in body
|
| May 12, 2021 at 20:02 | comment | added | Himanshu Bansal | If I find some typos/mistakes or grammatical errors which I can fix but still it need 6 characters to change to submit the request. How to fix that? | |
| Oct 17, 2020 at 11:13 | history | edited | Sonic the Anonymous Hedgehog | CC BY-SA 4.0 |
Can't exactly use filters on the vast majority of sites as they have significantly fewer edits (and a much smaller queue size); it's an SO thing mostly
|
| Sep 7, 2020 at 4:43 | history | edited | Sonic the Anonymous Hedgehog | CC BY-SA 4.0 |
Move to a better spot
|
| Sep 7, 2020 at 1:43 | history | edited | Braiam | CC BY-SA 4.0 |
Made the suggestion about using filters it's own introductory paragraph, upgrading skip to the first position.
|
| Sep 6, 2020 at 21:20 | history | edited | Sonic the Anonymous Hedgehog | CC BY-SA 4.0 |
added 25 characters in body
|
| Jun 3, 2020 at 13:30 | history | edited | CommunityBot |
Commonmark migration
|
|
| S Dec 17, 2017 at 12:30 | history | suggested | CommunityBot | CC BY-SA 3.0 |
Another anonymous editor (not gparyani) with an active account on SO and MSE since July 2017. Guess who I am
|
| Dec 17, 2017 at 11:34 | review | Suggested edits | |||
| S Dec 17, 2017 at 12:30 | |||||
| S Oct 25, 2017 at 17:29 | history | suggested | CommunityBot | CC BY-SA 3.0 |
Accept -> Approve; add in note about Markdown view being shown for link changes
|
| Oct 25, 2017 at 17:23 | review | Suggested edits | |||
| S Oct 25, 2017 at 17:29 | |||||
| Mar 20, 2017 at 10:30 | history | edited | CommunityBot |
replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
|
|
| Feb 19, 2017 at 22:23 | comment | added | Braiam | @KateGregory the help center explicitly states those edits as common reasons of why to edit a post "When should I edit posts? [...] Some common reasons for edits are: [...] to correct minor mistakes or add addendums / updates as the post ages" Through, maybe the example should be "This only works with Windows 8" instead. | |
| Feb 19, 2017 at 19:56 | comment | added | Kate Gregory | Wait, "Edits that attempt to add clarification to an answer, like “this doesn’t work in Windows 8”, or addendums to the post should be approved." - these I reject as attempts to reply. Unless the edit summary makes it clear they are bringing in info from comments, this kind of edit is not an Accept in my opinion. | |
| Feb 19, 2017 at 15:01 | history | edited | Cai | CC BY-SA 3.0 |
deleted 12 characters in body
|
| Feb 19, 2017 at 14:17 | history | edited | Braiam | CC BY-SA 3.0 |
This is MSE, it should be a mirror/extension of the help center https://meta.stackexchange.com/help/editing guidance. As such, it should be generic enough to be applied to all sites.
|
| Feb 19, 2017 at 14:12 | history | edited | Braiam | CC BY-SA 3.0 |
This is MSE, it should be a mirror/extension of the help center https://meta.stackexchange.com/help/editing guidance.
|
| Mar 14, 2016 at 16:14 | history | edited | Deduplicator | CC BY-SA 3.0 |
not all code-fixes in questions are bad. And community-wiki-posts allow far more radical changes
|
| Feb 23, 2015 at 17:29 | comment | added | bfavaretto | @Qsigma That would be considered altering the original answer too much. The preferred solution for this is to comment on the answer, and let the author update it (unless it's a Community Wiki). If the author doesn't update himself, then I believe it would be okay to edit. | |
| Feb 23, 2015 at 9:48 | comment | added | Qsigma | Why does the guideline recommend rejection of: "Edits that attempt to add clarification to an answer, like “this doesn’t work in Windows 8”," ? IMO opinion that stops us from 'future proofing' old answers: those that were written for Linux or Windows 7 for example. | |
| Dec 13, 2014 at 20:47 | history | edited | bjb568 | CC BY-SA 3.0 |
added 106 characters in body
|
| Nov 15, 2014 at 18:00 | history | edited | Wrzlprmft | CC BY-SA 3.0 |
Updating to the new rejection reasons and formatting.
|
| Apr 24, 2014 at 13:39 | history | edited | CommunityBot |
Migration of MSO links to MSE links
|
|
| May 20, 2013 at 19:01 | comment | added | Rachel | @djechlin Create a separate Answer for reviewing tag wiki edits, and add a note at the top of this answer explaining that there are two types of Edits for review (normal posts and tag wikis), and link to the tag wiki answer. | |
| May 20, 2013 at 12:06 | history | bounty ended | Rachel | ||
| May 17, 2013 at 17:21 | comment | added | djechlin | I personally think it's a little more organized to separate them. I think more value is added from clear titles than a 1-1 correspondence between review queue / answer here, in particular because I think it really, really should jump out to perusers of this thread that we have comprehensive guidelines on reviewing tag wiki edits. But yes at minimum we need to complete integrating that into this answer. | |
| May 17, 2013 at 16:54 | comment | added | djechlin | Motion to add a separate answer for tag wiki edits (or queue entirely honestly??) They're really distinct and both should be covered in this thread alone. | |
| May 17, 2013 at 16:53 | history | edited | djechlin | CC BY-SA 3.0 |
added 153 characters in body
|
| May 17, 2013 at 0:33 | history | edited | Kate Gregory | CC BY-SA 3.0 |
added 891 characters in body
|
| May 16, 2013 at 21:54 | history | edited | bfavaretto | CC BY-SA 3.0 |
Added link to discussion on tag wikis, as suggest on (now purged) comments
|
| May 13, 2013 at 13:45 | history | edited | Kate Gregory | CC BY-SA 3.0 |
added 407 characters in body
|
| May 13, 2013 at 13:35 | history | edited | Danny Beckett | CC BY-SA 3.0 |
deleted 2 characters in body
|
| Jan 27, 2013 at 16:35 | history | edited | Arjan | CC BY-SA 3.0 |
Note about URLs -- see the nasty http://stackoverflow.com/review/suggested-edits/208367
|
| Jan 27, 2013 at 16:25 | history | edited | Kate Gregory | CC BY-SA 3.0 |
added 613 characters in body
|
| Dec 12, 2012 at 15:34 | history | edited | gnat | CC BY-SA 3.0 |
deleted 1 characters in body
|
| Nov 13, 2012 at 15:48 | history | edited | psubsee2003 | CC BY-SA 3.0 |
added bullet point for rejecting edits to code in questions
|
| Nov 13, 2012 at 15:38 | history | edited | Joshua Dwire | CC BY-SA 3.0 |
corrected spelling
|
| S Nov 13, 2012 at 12:46 | history | answered | bfavaretto | CC BY-SA 3.0 | |
| S Nov 13, 2012 at 12:46 | history | made wiki | Post Made Community Wiki by bfavaretto |