The following is a set of guidelines for contributing to Ant Design. Please spend several minutes reading these guidelines before you create an issue or pull request.
Code of Conduct#
We have adopted a Code of Conduct that we expect project participants to adhere to. Please read the full text so that you can understand what actions will and will not be tolerated.
All work on Ant Design happens directly on GitHub. Both core team members and external contributors send pull requests which go through the same review process.
According to our release schedule, we maintain two branches,
feature. If you send a bugfix pull request, please do it against the
master branch, if it's a feature pull request, please do it against the
Before you report a bug, please make sure you've searched existing issues, and read our FAQ.
Proposing a Change#
If you intend to change the public API or introduce new feature, we also recommend you use our issue helper to create a feature request issue.
If you want to help on new API, please reference API Naming Rules to name it.
Your First Pull Request#
Working on your first Pull Request? You can learn how from this free video series:
To help you get your feet wet and get you familiar with our contribution process, we have a list of good first issues that contain bugs or small features that have a relatively limited scope. This is a great place to get started.
If you decide to fix an issue, please be sure to check the comment thread in case somebody is already working on a fix. If nobody is working on it at the moment, please leave a comment stating that you intend to work on it so other people don't accidentally duplicate your effort.
If somebody claims an issue but doesn't follow up for more than two weeks, it's fine to take over it but you should still leave a comment.
Sending a Pull Request#
The core team is monitoring for pull requests. We will review your pull request and either merge it, request changes to it, or close it with an explanation.
Before submitting a pull request, please make sure the following is done:
Fork the repository and create your branch from the correct branch.
npm installin the repository root.
If you've fixed a bug or added code that should be tested, add tests!
Ensure the test suite passes (npm run test). Tip:
npm test -- --watch TestNameis helpful in development.
npm test -- -uto update the jest snapshots and commit these changes as well (if there are any updates).
Ensure the UI change passes
npm run test-image，Run
npm run test-image -- -uto update UI snapshots and commit these changes as well (if there are any updates), UI test base on Docker, need download the corresponding installation according to the platform
Make sure your code lints (npm run lint). Tip: Lint runs automatically when you
git commit(Use Git Hooks).
Sending a Pull Request to react-component:
Since antd's components are based on react-component, sometimes you may need to send pull request to the corresponding react-component repository. If it's a bugfix pull request, after it's merged, the core team will release a patch release for that component as soon as possible, then you only need to reinstall antd in your project to get the latest patch release. If it's a feature pull request, after it's merged, the core team will release a minor release, then you need raise another pull request to Ant Design to update dependencies, document and TypeScript interfaces (if needed).
After cloning antd, run
npm install to fetch its dependencies. Then, you can run several commands:
npm startruns Ant Design website locally.
npm run lintchecks the code style.
npm testruns the complete test suite. (Make sure the
NODE_ENVenvironment variable is unset, or it may causing some problems.)
npm run compilecompiles TypeScript code to the
npm run distcreates UMD build of antd.
Being a collaborator#
If you are an active contributor and are willing to work with Ant Design Team in our opensource workflow, you can apply to be a outside collaborator.