Open-Source Contributing Guidelines (CONTRIBUTING.md) Template
markdown
1 day ago
·
65 lines
·
8 views
Contributing to Project Name
Thank you for investing your time in improving this open-source project!
๐ Code of Conduct
This project adheres to the Contributor Covenant. By participating, you are expected to uphold this code. Please report unacceptable behavior to security@example.com.
๐ Getting Started
Prerequisites
- Node.js >= 20.0.0
- Git
Local Setup
# 1. Fork the repo and clone your fork
git clone https://github.com/<your-username>/project-name.git
cd project-name
# 2. Install dependencies
npm install
# 3. Create development environment file
cp .env.example .env
# 4. Run local database migrations
npm run db:migrate
# 5. Start development server
npm run dev
๐ฟ Branching & Commit Conventions
Branch Names
feat/short-description(new features)fix/issue-description(bug fixes)docs/page-name(documentation improvements)perf/component-name(performance improvements)
Conventional Commits
Use semantic commit messages:
feat(auth): add passkey authentication supportfix(editor): prevent cursor jump on autosaveperf(db): add composite index on user_id and created_atdocs(readme): update deployment instructions
๐งช Testing Guidelines
Before opening a pull request, ensure all tests pass:
npm run test
npm run test:coverage
Pull requests without unit or integration tests for new features will not be merged.
1# Contributing to Project Name
3Thank you for investing your time in improving this open-source project!
5## ๐ Code of Conduct
7This project adheres to the Contributor Covenant. By participating, you are expected to uphold this code. Please report unacceptable behavior to `security@example.com`.
9---
11## ๐ Getting Started
13### Prerequisites
14- Node.js >= 20.0.0
15- Git
17### Local Setup
18```bash
19# 1. Fork the repo and clone your fork
20git clone https://github.com/<your-username>/project-name.git
21cd project-name
23# 2. Install dependencies
24npm install
26# 3. Create development environment file
27cp .env.example .env
29# 4. Run local database migrations
30npm run db:migrate
32# 5. Start development server
33npm run dev
34```
36---
38## ๐ฟ Branching & Commit Conventions
40### Branch Names
41- `feat/short-description` (new features)
42- `fix/issue-description` (bug fixes)
43- `docs/page-name` (documentation improvements)
44- `perf/component-name` (performance improvements)
46### Conventional Commits
47Use semantic commit messages:
48- `feat(auth): add passkey authentication support`
49- `fix(editor): prevent cursor jump on autosave`
50- `perf(db): add composite index on user_id and created_at`
51- `docs(readme): update deployment instructions`
53---
55## ๐งช Testing Guidelines
57Before opening a pull request, ensure all tests pass:
59```bash
60npm run test
61npm run test:coverage
62```
64Pull requests without unit or integration tests for new features will not be merged.
Replies 0
No replies yet
Every reply is a note. Start a discussion, ask a question, or attach a code snippet.
Notification