New users golfing code

The last two Suggested Edit reviews I have reviewed, they were easy rejects. Both were from a new user (the same), and both were golfing/"fixing" the code. I admit to have done this before, but a while ago. I therefore propose that there should be a new box when editing a post.

Your edit will be placed in a queue until it is peer reviewed.

We welcome all constructive edits, but please make them substantial. Avoid trivial edits unless absolutely necessary.

I suggest there should be a last line:

Your edit will be placed in a queue until it is peer reviewed.

We welcome all constructive edits, but please make them substantial. Avoid trivial edits unless absolutely necessary. Do not edit the code unless this is Community Wiki, please [comment](link-to-comment).

• Not sure if this can be adjusted just for PPCG. Also, this particular user doesn't have enough rep to post comments. – Dennis Jul 31 '16 at 20:11
• @Dennis I know. Even if they can't comment, they shouldn't make an edit like that. – NoOneIsHere Jul 31 '16 at 20:13
• I'm not saying edits like those should be suggested, but asking the user to comment instead when he can't is a bit weird. Maybe Once you earn 50 reputation, you'll be able to comment everywhere. would be better. – Dennis Jul 31 '16 at 20:19
• Might be worth adding this to this thread which I'm told is currently being reviewed by the CMs. – Martin Ender Jul 31 '16 at 21:13
• @Dennis The 50 rep commenting system is there for a reason; comments-in-posts are an easy reject (or accept and edit). – Erik the Outgolfer Aug 1 '16 at 7:15
• Your edit should not be an edit but a separate question. – Peter Taylor Aug 11 '16 at 7:57

• I can submit 'f' as my answer and I can win... Doesn't seem right. Actually, you couldn't. High-rep users and moderators can delete invalid answers. Low-rep users can downvote and flag. The challenge poster can choose not to accept it. Generally this community gets rid of invalid posts pretty quickly. – James Aug 1 '16 at 0:10