This directory contains GitHub-specific files that control various aspects of the repository's behavior on GitHub.
.github/
├── ISSUE_TEMPLATE/ # Templates for creating new issues
│ ├── bug_report.md # Template for reporting bugs
│ ├── feature_request.md # Template for requesting features
│ ├── documentation_issue.md # Template for documentation issues
│ ├── config.yml # Configuration for the issue templates
│ └── README.md # Documentation for issue templates
├── PULL_REQUEST_TEMPLATE/ # Templates for creating PRs
│ ├── default.md # Detailed template for general PRs
│ ├── bugfix.md # Template for bug fix PRs
│ ├── feature.md # Template for feature PRs
│ ├── documentation.md # Template for documentation PRs
│ └── README.md # Documentation for PR templates
├── workflows/ # GitHub Actions workflows
│ └── pull-request.yml # PR validation workflow
├── CODEOWNERS # Automatic reviewer assignments
├── CONTRIBUTING.md # Contributing guidelines
├── CODE_OF_CONDUCT.md # Code of conduct for contributors
├── SECURITY.md # Security policy and reporting
├── pull_request_template.md # Default PR template
└── README.md # This file
Issue templates provide structured formats for users to report bugs, request features, or highlight documentation issues. These templates ensure that necessary information is provided when creating new issues.
PR templates guide contributors on how to structure their pull request descriptions. They include sections for describing changes, linking to issues, and confirming that tests have been performed.
GitHub Actions workflows automate testing, building, and other CI/CD processes. These workflows help ensure code quality and catch issues before they're merged.
The CODEOWNERS file automatically assigns reviewers to pull requests based on which files are changed.
- CONTRIBUTING.md: Guidelines for contributing to the project
- CODE_OF_CONDUCT.md: Rules and standards for participation
- SECURITY.md: Instructions for reporting security vulnerabilities
When updating these files, consider:
- Keeping templates concise but thorough
- Ensuring workflows are efficient and not unnecessarily complex
- Keeping documentation up-to-date with any changes