Skip to content

Docs: Define expectations around ownership of issues and PRs #19900

@nzakas

Description

@nzakas

Docs page(s)

https://eslint.org/docs/latest/contribute/work-on-issue

What documentation issue do you want to solve?

Lately, we've had several instances of two people submitting a PR for the same change and then arguing over who's PR should be accepted. The latest example is eslint/markdown#450.

While we've had norms around this, it's not easy for new contributors to pick up on those norms, requiring more time from the team to disentangle these situations.

What do you think is the correct solution?

Document the norms we expect around issue and PR ownership.

Participation

  • I am willing to submit a pull request for this change.

Additional comments

No response

Metadata

Metadata

Assignees

Labels

acceptedThere is consensus among the team that this change meets the criteria for inclusiondocumentationRelates to ESLint's documentation

Type

No type

Projects

Status

Complete

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions