Skip to content

Create community standards files #29

Description

@MessiasLima

Description

The repository is missing essential community standards files that help contributors understand how to engage with the project. These files improve the contributor experience and are recognized by GitHub's community standards checklist.

  • Create the following files:

    • CODE_OF_CONDUCT.md — Adopt the Contributor Covenant v2.1 at the repository root
    • CONTRIBUTING.md — Contribution guidelines referencing existing conventions in AGENTS.md
    • SECURITY.md — Instructions for reporting security vulnerabilities
    • .github/ISSUE_TEMPLATE/ — YAML-based issue forms using GitHub's form schema
      • config.yml — Template chooser configuration (disable blank issues, add contact links)
      • bug_report.yml — Bug report form with input, textarea, dropdown, and checkbox fields
      • feature_request.yml — Feature request form with input, textarea, and dropdown fields
    • .github/PULL_REQUEST_TEMPLATE.md — Standard PR template with checklist
  • Scope and constraints

    • Issue forms use .yml (YAML form schema), not legacy .md templates
    • All content should align with existing project conventions from AGENTS.md
    • The code of conduct should use the standard Contributor Covenant v2.1

Acceptance criteria

  • CODE_OF_CONDUCT.md exists at the repository root with Contributor Covenant v2.1
  • CONTRIBUTING.md exists at the repository root with setup, build, and PR guidelines
  • SECURITY.md exists at the repository root with a vulnerability reporting process
  • .github/ISSUE_TEMPLATE/config.yml exists with blank_issues_enabled: false and relevant contact links
  • .github/ISSUE_TEMPLATE/bug_report.yml exists using GitHub form schema with appropriate fields (description, steps to reproduce, expected vs actual behavior, environment)
  • .github/ISSUE_TEMPLATE/feature_request.yml exists using GitHub form schema with appropriate fields (problem, solution, alternatives)
  • .github/PULL_REQUEST_TEMPLATE.md exists with a description section and contributor checklist

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    Status
    Done

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions