153

The Situation

For those of us with <2k reputation, it can be tough to see your diligently submitted edit get rejected for this reason:

rejected edit due merge conflict message

"This edit conflicted with a subsequent edit."

The thing is, the edit wasn't really 'rejected'. It was actually just a merge conflict. No big deal right? Except that it hurts your prized editorial statistics.

The Proposal

Change the merge conflict categorization from "rejected" to "cancelled".

Additionally, "cancelled" edits should not count against your (prized) edit statistics.

What does the community think?

Note: I am only slightly biased as I did just get rejected in this manner, BUT if you look through the merge conflict link there seems to be some traction for this idea in the comments section.

12
  • 73
    Technically, rejected edits caused by a conflict don't count towards the edit ban but I do like the idea of calling it something different.
    – BSMP
    Commented Apr 6, 2019 at 2:14
  • 8
    Second. Change this type to cancel is easier for editors to check their suggestions too.
    – Til
    Commented Apr 6, 2019 at 4:50
  • 6
    @BSMP imo that's the perfect reason for why it should be reclassified.
    – TheWanderer
    Commented Apr 6, 2019 at 11:36
  • 10
    Not "canceled" but "conflicted" can be better to understand.
    – randomuser5215
    Commented Apr 6, 2019 at 11:49
  • 23
    Technically there is a review result called „invalidated“. This could be reused here.
    – User that hates AI
    Commented Apr 6, 2019 at 12:18
  • 7
    @smileycreations15 I prefer "cancelled" - it's the end result. Similarly, "invalidated" works the same way. But "conflicted" is the state that would lead to cancellation or invalidation. I think it's more consistent to just give the end states - "approved" and "rejected" are end states already.
    – VLAZ
    Commented Apr 7, 2019 at 13:35
  • 10
    "Cancelled" with two "l"s? Hold on a minute chaps, since when did programmers start speaking the Queen's English?
    – Andrew Grimm
    Commented Apr 8, 2019 at 8:00
  • 14
    @AndrewGrimm it's the only proper way to program. You start dropping the u from words, rearranging the re suffix and next thing you know you are dropping tea in the harbor. Which we all know just leads to bugs.
    – VLAZ
    Commented Apr 8, 2019 at 13:58
  • 4
    Does the "reject and edit" option generate the same reject-message? That would need to stay in place in my opinion, since if someone consciously chooses to reject a suggested edit and instead suggest an alternative, it is rejected.
    – Adriaan
    Commented Apr 8, 2019 at 14:32
  • Related question: meta.stackoverflow.com/q/290903/9614249
    – Increasingly Idiotic
    Commented Apr 8, 2019 at 18:20
  • 2
    These are suggestions, suggestions get approved or rejected; they may be invalidated by something else. Suggestions aren't canceled nor completed.
    – Braiam
    Commented Aug 14, 2020 at 23:56
  • 3
    I'm personally eagerly awaiting the status on this feature-request. I'm a "bad" editor, by my "editorial statistics". I do not wish to become a worse editor, so I stopped editing. I may start editing again, once I know I'm no longer a "bad" editor :)
    – Scratte
    Commented Aug 15, 2020 at 7:10

2 Answers 2

Reset to default
21

Suggested edits that are canceled by the Community bot due to a conflicting subsequent edit are now categorized as "Canceled" instead of "Rejected". This change has been applied retroactively so prior subsequent edit rejections will now be marked as "Canceled/Cancel" when viewing suggestions on a user profile or on the individual suggested edit view. In addition, these changes will be reflected in editorial statistics which now separates out the number of edits that have been canceled from those rejected.

Suggested edit review task view with editorial statistics expanded Suggested edit review task view with editorial statistics expanded

Please let us know if there are any issues when reviewing suggested edits that involve merge conflicts or the Community bot.

2
  • The Stacks style guide would suggest the edit stats are complete sentences and should end with a period.
    – bad_coder
    Commented Jul 5 at 1:34
  • 1
    @bad_coder Great catch! A period has been added to the end of the sentences.
    – tobi StaffMod
    Commented Jul 9 at 12:49
-10

Based on our current roadmap, this isn't work that we will take on, as it doesn't coincide with functional areas that we plan to improve in the near future. We recognize there is community support for this, but unfortunately, we can't prioritize it at this time. 

2
  • 1
    That's very unfortunate in my opinion. But I assume the reasons must be that are already enough users willing to edit.
    – Scratte
    Commented Mar 21, 2021 at 21:41
  • 5
    If you don't mind, what is being prioritized? Additionally, how hard would it be to implement from a developers standpoint? This is a pretty big problem which I actually encountered myself once, so that's why I'm asking.
    – 10 Rep
    Commented Mar 22, 2021 at 0:20

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .