Thanks to visit codestin.com
Credit goes to github.com

Skip to content

PR requirement checking leaves a bad impression for small fixes #16

@cassidyjames

Description

@cassidyjames

I contributed a small typo fix I noticed when reading through the GitHub CLI docs, and was immediately told the PR was not valid and would be closed if I didn't link it to an existing issue with a help wanted label.

I completely understand the need for automated PR triage, but this left a bad taste in my mouth; I'd just spent a moment trying to be a good open source citizen, but was told my effort was wasted or I'd have to go through an unknown process to create a new issue, potentially have a maintainer acknowledge and triage that issue, and then I would be allowed to contribute.

In the end, a human was able to jump in and approve the PR anyway (shout out @williammartin for the rapid response time!), but it left a bad first impression on me as a first-time contributor to the repo.

I'm not sure what the solution is; perhaps it could just be some copy finessing for the bot message that clarifies something like:

Small, obvious, and self-contained fixes may still be merged and approved by a maintainer without a linked issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions