Chapter 135: Contribution Guide
Core Idea
Guidelines and instructions for contributing to the Lucide project.
Key Concepts
- Make your commit messages as descriptive as possible. Include as much information as you can. Explain anything that the file diffs themselves won’t make apparent.
- Document your pull request. Explain your fix, link to the relevant issue, add screenshots when adding new icons.
- Make sure the target of your pull request is the relevant branch. Most of bug fixes or new feature should go to the
main branch.
- Include only related work. If your pull request has unrelated commits, it won't be accepted.
- Local:
http://localhost:3000/
- Network:
http://192.168.x.x:3000/
Code Examples
pnpm install # Install dependencies, including the workspace packages
- What it demonstrates: Contribution Guide usage pattern from the official Lucide docs.
Key Takeaways
- Make your commit messages as descriptive as possible. Include as much information as you can. Explain anything that the file diffs themselves won’t make apparent.
- Document your pull request. Explain your fix, link to the relevant issue, add screenshots when adding new icons.
- Make sure the target of your pull request is the relevant branch. Most of bug fixes or new feature should go to the
main branch.
- Include only related work. If your pull request has unrelated commits, it won't be accepted.
- Local:
http://localhost:3000/
Connects To
- Contributing & Design Guides: part of the Contributing & Design Guides section of the Lucide docs.