Skip to content

[2026 Community] Publish contribution difficulty labels and starter issues guide #909

Description

@Nanle-code

Objective

Clarify good-first-issue standards and difficulty labels for community contributors.

Target area

community docs and labels

Acceptance criteria

  • The objective is implemented with clear handling for invalid input, unsupported environments, and failure paths.
  • Automated tests cover the primary flow, at least one boundary case, and at least one failure case.
  • User-facing documentation or developer guidance is updated, including compatibility, security, or migration notes where applicable.
  • Pull requests that address this issue must keep the branch free of merge conflicts with the target branch.
  • All continuous integration checks must pass before the pull request may be merged; failing, pending, or skipped required checks are not acceptable for merge.

Pull request requirements

  • All continuous integration checks must pass before a pull request may be merged.
  • The branch must be free of merge conflicts with the target branch at the time of merge.
  • Do not request merge with failing workflows, skipped required checks, or unresolved conflicts.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions