We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:
- Reporting an issue
- Discussing the current state of the code
- Submitting a fix
- Proposing new features
The code of conduct is described in CODE_OF_CONDUCT.md
.
All changes happen through pull requests. Pull requests are the best way to propose changes. We actively welcome your pull requests and invite you to submit pull requests directly here, and after review, these can be merged into the project.
This project is using the conventional commits standard. Please follow these steps to ensure your commit messages are standardized:
- Make sure your shell path is in the root of the project (not inside any of the packages).
- Run
npm i
. - Stage the files you are commiting with
git add [files]
. git commit -m < you_message >
:- Prefix commit message with
fix:
orfeat:
according to type of commit. - Write a short, imperative tense description of the change.
- Provide a issue number if your're creating pull request related the specific issue
- Prefix commit message with
- Fork the repo and create your branch.
- If you've added code that should be tested, add some test examples.
- Ensure to describe your pull request.
git add [files]
git commit -m 'your commit message'
git push <branch_name>
- Run
npm install
- Run
npm run dev
- http://localhost:3000
We use GitHub issues to track public bugs. Please ensure your description is clear and has sufficient instructions to be able to reproduce the issue. Report a bug by opening a new issue; it's that easy!
- Q: [The Question?]
- A: [The Answer!]
Great Feature Requests tend to have:
- A quick idea summary.
- What & why you wanted to add the specific feature.
- Additional context like images, links to resources to implement the feature etc, etc.
By contributing to WildDuck Ui, you agree that your contributions will be licensed under the LICENSE file.