56 lines (39 loc) · 1.62 KB

Contributing to Wisp CSS

Thanks for your interest in contributing! 🎉

Getting Started

Fork wispcss/wisp-css and clone your fork.
Install dependencies (see the README for setup instructions).
Create a branch from main:
```
git checkout -b feat/your-feature-name
```
Make your changes, commit, and push to your fork.
Open a Pull Request against main.

How to Contribute

Bug fixes — check open issues labeled bug.
Features — look for issues labeled enhancement or good first issue.
Docs — typos, clarity, and missing examples are always welcome.
Tests — improving coverage is never a bad idea.

Pull Request Guidelines

Keep PRs focused — one fix or feature per PR.
Link related issues in your PR description (Closes #123).
Make sure all checks pass before requesting review.
At least one approving review is required before merging.

Commit Messages

We follow Conventional Commits:

feat: add utility class for gap spacing
fix: correct specificity issue in reset
docs: update usage examples in README
chore: bump dev dependencies

Reporting Bugs

Open an issue and include:

Steps to reproduce
Expected vs. actual behavior
Browser/environment info
A minimal reproduction if possible

Requesting Features

Open an issue with the enhancement label and describe the problem you're solving and your proposed solution.

All contributions are subject to the MIT License.