Skip to content

prepare a list of copy/paste comments we can use when dealing with low quality contributions #1168

Description

@derberg

we would have such a list in https://github.com/asyncapi/spec/wiki so it is easy for any maintainer to copy and paste.

for example, have a respectful and educational copy/paste comment for people who open a PR that has no issue or the issue was not approved by maintainers as valid to work on.

it's too much basically, over last weeks I had to write a lot of these messages

Activity

  1. derberg commented on Jan 15, 2026

    @derberg
    MemberAuthor

    message when PR is opened if there is still no consensus in issue and ai was used:

    Thanks for the contribution. I’m closing this PR because the related issue was not opened for contribution, and there is no clear consensus on how this should be solved.
    
    Please also note that contributions to specification-level features cannot be done using AI-generated content and require direct industry expertise and prior involvement in the domain.
    
    Before opening issues or pull requests, make sure to read [the contribution guidelines](https://github.com/asyncapi/spec/blob/master/CONTRIBUTING.md) carefully, as they explain what kinds of changes are accepted and the expected process.
    
  2. derberg commented on Jan 15, 2026

    @derberg
    MemberAuthor

    message when PR is opened without issue and ai

    Thanks for the contribution. I’m closing this PR because no issue was created to discuss the change before opening the pull request. There is also already a clear consensus on how this should be solved.
    
    Please note that contributions affecting specification-level features require direct industry expertise and cannot be based on AI-generated content.
    
    Before opening issues or pull requests, please make sure to read [the contribution guidelines](https://github.com/asyncapi/spec/blob/master/CONTRIBUTING.md), which explain the required process and scope of acceptable contributions.
    
  3. derberg commented on Jan 15, 2026

    @derberg
    MemberAuthor

    message when PR is opened but issue not approved, but not spec related

    Thanks for the contribution. I’m closing this PR because, while there is an existing issue, it was not approved or opened for contribution before the pull request was submitted.
    
    Please make sure to follow [the contribution guidelines](https://github.com/asyncapi/spec/blob/master/CONTRIBUTING.md), which explain when issues are considered ready for implementation and when pull requests are appropriate.
    
  4. bhavikcodes commented on Jan 17, 2026

    @bhavikcodes

    hey! i would like to work on this enhancement.

  5. bhavikcodes commented on Jan 17, 2026

    @bhavikcodes

    we would have such a list in https://github.com/asyncapi/spec/wiki so it is easy for any maintainer to copy and paste.

    for example, have a respectful and educational copy/paste comment for people who open a PR that has no issue or the issue was not approved by maintainers as valid to work on.

    it's too much basically, over last weeks I had to write a lot of these messages

    hey! I had completed the task, you can review it here https://github.com/asyncapi/spec/wiki/%231168-list-of-copy-paste-comments-for-low-quality-contributions

  6. Amythystx commented on Jan 19, 2026

    @Amythystx

    Hi !
    Thanks for putting this list together — it’s very helpful and well structured.

    While reviewing it, I noticed a few additional scenarios that could potentially be added in the future (for example: missing reproduction steps, non-responsive contributors, or documentation-only PRs with unclear intent). Grouping templates by category might also make them easier to scan.

    No changes needed from my side right now — just sharing feedback in case it’s useful. Happy to help with follow-ups if needed ..

  7. Himanishrana commented on Jan 20, 2026

    @Himanishrana

    Hi everyone! This is my first contribution here

    I’ve read the contribution guidelines and reviewed the existing wiki page and the feedback shared above. I’d like to help by making a small, additive update focused on usability — grouping templates by category, adding brief “when to use” guidance, and possibly adding one or two common scenarios mentioned in the feedback.

    I’ll keep the changes editorial-only and non-disruptive. I’ll share a concrete draft once ready.

  8. Himanishrana commented on Jan 20, 2026

    @Himanishrana

    Hi! I put together a small, editorial-only update to the wiki that incorporates the suggested additional scenarios and groups templates by category for easier scanning.

    I don’t have write access to the wiki, so I’m attaching the patch here in case a maintainer would like to apply it.

    Happy to adjust, split, or simplify anything if needed — thanks!

    0001-Improve-structure-and-add-additional-copy-paste-temp.patch

  9. github-actions commented on May 21, 2026

    @github-actions

    This issue has been automatically marked as stale because it has not had recent activity 😴

    It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

    There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

    Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

    Thank you for your patience ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions