Skip to content

Latest commit

 

History

History
77 lines (49 loc) · 3.43 KB

CONTRIBUTING.md

File metadata and controls

77 lines (49 loc) · 3.43 KB
Raw

English | 简体中文

Contributing

Thank you for taking your time to contribute and make this project better! Here are some guidelines to help you get started. Please make sure to take a moment and read through them before submitting your contributions.

Code of Conduct

This project is governed by the Contributor Covenant Code of Conduct. By participating, you are expected to adhere to it.

Open Development

All work happens directly on GitHub. Both core team members and external contributors send pull requests which go through the same code review process.

Semantic Versioning

This project follows semantic versioning. We release patch versions for bug fixes or other changes that do not change the behavior of the API, minor versions for new features that are backward-compatible, and major versions for any breaking changes.

Every significant change is documented in the changelog file.

Reporting Issues

We use Github issues for bug reports and feature requests. Before reporting an issue, please make sure you have searched for similar issues as they may have been already answered or being fixed. For bug reporting, please include the minimum code that can be used to reproduce the problem. For feature request,

Sending a pull request

  1. Fork the repository，and create your branch from main. For new feature, please submit your changes directly to the feature branch. Other changes should go against main branch.
  2. Use pnpm install install the dependencies
  3. Use pnpm run dev start project,RUN pnpm run play start the playground,RUN pnpm run docs to write docs。
  4. Make changes to the codebase. Please add tests if applicable.
  5. Make sure the test suite passes with pnpm run test.
  6. Use pnpm run test:ci to RUN CI tests before you commit your code.
  7. Commit your changes, adhering to the Commit Guidelines.
  8. Open a new pull request,referencing corresponding issues if available.

Commit Guidelines

Commit messages are required to follow the conventional-changelog standard:

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

👉 Commit example

Commit types

The following is a list of commit types:

  • feat: A new feature or functionality
  • fix: A bug fix
  • docs: Documentation only changes
  • style: Code formatting or component style changes
  • refactor: Code changes that neither fixes a bug nor adds a feature.
  • perf: Improve performance.
  • test: Add missing or correct existing tests.
  • chore: Other commits that don’t modify src or test files.

OnuUI Repository Structure

This repository is managed by pnpm and includes the following packages：

  1. onu-ui: UI component main
  2. docs: Component documentation site
  3. @onu-ui/components: UI component library
  4. @onu-ui/preset: UI component preset
  5. @onu-ui/utils: UI component utility
  6. @onu-ui/cli: UI component CLI

License

By contributing your code to the repository, you agree to license your contribution under the MIT license.