Problem/Motivation

#3362864: [Ignore] In space (and/or this issue), no one can hear patches scream VI
#3379520: [Ignore] In space (and/or this issue), no one can hear patches scream VIII
Steps to reproduce
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
Release notes snippet
Issue fork drupal-3369993
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
spokjeComment #3
spokjeComment #4
spokjeComment #5
spokjeComment #6
spokjeComment #7
spokjeComment #8
spokjeComment #9
spokjeComment #10
spokjeComment #11
spokjeComment #12
spokjeComment #13
spokjeComment #14
spokjeComment #15
spokjeComment #16
spokjeComment #17
spokjeComment #18
spokjeComment #19
spokjeComment #20
spokjeComment #21
spokjeComment #24
spokjeComment #25
spokje@sonam_sharma at Smashing Infolabs: Thanks for your smashing contribution of an empty MR in a clearly marked [ignore] issue.
May you step on many lego bricks with bare feet.
Comment #26
spokjeComment #27
volkswagenchick@sonam_sharma I see you have opened a merge request on an issue that is in a space that has asked to be ignored. Indicated you did bot read or pay attention to the issue summary.
I realize I have already informed you in other issues about this same behavior, but I am posting again for transparency.
The number of issues you, and your organization, have posted in the last few days (even yesterday) leads other contributors to think you may be attempting to gamify the Drupal attribution system.
When you open a merge request or post a file it ticks the credit box for attribution and creates more work for maintainers when they close the issues. Please refrain from opening a merge request unless you are working on code.
I am going to go through some of the issues you are working on and give you individual examples on issue queue etiquette and how you can better improve your contributor experience working within the community.
Here is a list of resources to help you on your contribution journey, thanks!
Issue Queue Etiquette
Contributor tasks
Adding tags to issues and using tags
How is credit granted for Drupal core issues
I have unticked the attribution box, as you did not contribute to the conversation, let me know if you have any questions.
~AmyJune, Core Mentor and CWG Community Health team member
Comment #28
spokjeComment #29
spokjeComment #30
spokjeComment #31
spokjeComment #32
spokjeComment #33
spokjeComment #34
spokjeComment #35
spokjeComment #36
spokjeComment #37
spokjeComment #38
spokjeComment #39
spokjeComment #40
spokjeComment #41
spokjeComment #42
spokjeComment #43
spokjeComment #44
spokjeComment #45
spokjeComment #46
spokjeComment #47
spokjeComment #48
spokjeComment #49
spokjeComment #50
spokjeComment #51
spokjeComment #52
spokjeComment #53
spokjeComment #54
spokjeComment #55
spokjeComment #56
spokjeComment #57
spokjeComment #58
spokjeComment #59
spokjeComment #60
spokjeComment #61
spokjeComment #62
spokjeComment #63
spokjeComment #64
spokjeComment #65
spokjeComment #66
spokjeComment #67
spokjeComment #68
spokjeComment #69
spokjeComment #70
spokjeComment #71
spokjeComment #72
spokjeComment #73
spokjeComment #74
spokjeComment #75
spokjeComment #76
spokjeComment #77
spokjeComment #78
spokjeComment #79
spokjeComment #80
spokjeComment #81
spokjeComment #82
spokjeComment #83
spokjeComment #84
spokjeComment #85
spokjeComment #86
spokjeComment #87
spokjeComment #88
spokjeComment #89
spokjeComment #90
spokjeComment #91
spokjeComment #92
spokjeComment #93
spokjeComment #94
spokjeComment #95
spokjeComment #96
spokjeComment #97
spokjeComment #98
spokjeComment #99
spokjeComment #100
spokjeComment #101
spokjeComment #102
spokjeComment #103
spokjeComment #104
spokjeComment #105
spokjeComment #106
spokjeComment #107
spokjeComment #108
spokjeComment #109
spokjeComment #110
spokjeComment #111
spokjeComment #112
spokjeComment #113
spokjeComment #114
spokjeComment #115
spokjeComment #116
spokjeComment #117
spokje