Summary

• Welcome new contributors on their first issue or first PR with a short comment and link to CONTRIBUTING.
• Auto-label issues (e.g. bug, enhancement, documentation, good first issue, maintainer-only vs contributor-friendly) from title/body.
• Auto-label PRs (e.g. bug, enhancement, documentation) when opened/edited.
• Differentiate maintainer vs contributor: label issues as maintainer issue or contributor issue and PRs as maintainer PR or contributor PR based on who opened them (write/admin on repo = maintainer).
• Add CONTRIBUTING.md and issue templates (bug report, feature request) per project doc.

Why

• README says: "Pull requests are welcome. Found a bug? Open an issue." We should onboard contributors and make it clear what’s a bug vs enhancement and what’s for maintainers vs contributors.
• Auto-labeling keeps issues and PRs easier to triage. Separating maintainer vs contributor issues/PRs helps route and prioritise.

Implementation (done / to do)

• Add CONTRIBUTING.md with setup and guidelines.
• Workflow: welcome comment on first issue / first PR.
• Workflow: auto-label issues from keywords (bug, enhancement, doc, good first issue, maintainer-only / contributor-friendly).
• Workflow: auto-label issues as maintainer issue or contributor issue by repo permission (write/admin = maintainer).
• Workflow: auto-label PRs from title/body (bug, enhancement, documentation).
• Workflow: auto-label PRs as maintainer PR or contributor PR by repo permission.
• Issue templates: bug report and feature request with default labels.
• One-time: create repo labels (bug, enhancement, documentation, good first issue, maintainer-only, contributor-friendly, maintainer issue, contributor issue, maintainer PR, contributor PR) if they don’t exist.

Labels

• enhancement (or feature)
• contributor-friendly