# Welcome to Anki xiehanzi docs contributing guide Thank you for investing your time in contributing to our project! Any contribution you make will be reflected on [Anki xiehanzi](https://github.com/krmanik/Anki-xiehanzi) :sparkles:. In this guide you will get an overview of the contribution workflow from opening an issue, creating a PR, reviewing, and merging the PR. ## New contributor guide To get an overview of the project, read the [README](README.md) or visit webpage [Anki xiehanzi](https://github.com/krmanik/Anki-xiehanzi). Here are some resources to help you get started with open source contributions: - [Finding ways to contribute to open source on GitHub](https://docs.github.com/en/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github) - [Set up Git](https://docs.github.com/en/get-started/quickstart/set-up-git) - [GitHub flow](https://docs.github.com/en/get-started/quickstart/github-flow) - [Collaborating with pull requests](https://docs.github.com/en/github/collaborating-with-pull-requests) ## Getting started The project contains three parts 1. HSK tsv file which contains words and meaning of Chinese characters with pinyin and zhuyin. This is available as submodule in this project. 2. The Anki xiehanzi deck which can be imported into Anki. Download decks from [here](https://krmanik.github.io/Anki-xiehanzi/docs/gettings-started/download). 3. The web page which can be used as documentation as well as deck generation tool. The docs page created using [docusaurus.io](https://docusaurus.io/). View webpage [https://krmanik.github.io/Anki-xiehanzi] ### Issues #### Create a new issue If you spot a problem with the decks, wrong meaning, pinyin or zhuyin, [search if an issue already exists](https://docs.github.com/en/github/searching-for-information-on-github/searching-on-github/searching-issues-and-pull-requests#search-by-the-title-body-or-comments). If a related issue doesn't exist, you can open a new issue using a relevant [issue form](https://github.com/krmanik/Anki-xiehanzi/issues/new/choose). The PR for fix of issues related to HSK word lists can be submitted [here](https://github.com/krmanik/HSK-3.0-words-list). #### Solve an issue Scan through our [existing issues](https://github.com/krmanik/Anki-xiehanzi/issues) to find one that interests you. You can narrow down the search using `labels` as filters. As a general rule, we don’t assign issues to anyone. If you find an issue to work on, you are welcome to open a PR with a fix. ### Make Changes #### Make changes locally 1. Install Git 2. Fork the repository. - Using GitHub Desktop: - [Getting started with GitHub Desktop](https://docs.github.com/en/desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop) will guide you through setting up Desktop. - Once Desktop is set up, you can use it to [fork the repo](https://docs.github.com/en/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop)! - Using the command line: - [Fork the repo](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo#fork-an-example-repository) so that you can make your changes without affecting the original project until you're ready to merge them. 3. Install or update to **Node.js v16**. For more information, see [the development guide](contributing/development.md). 4. Create a working branch and start with your changes! ### Pull Request When you're finished with the changes, create a pull request, also known as a PR. - Fill the "Ready for review" template so that we can review your PR. This template helps reviewers understand your changes as well as the purpose of your pull request. - Don't forget to [link PR to issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue) if you are solving one. - Enable the checkbox to [allow maintainer edits](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/allowing-changes-to-a-pull-request-branch-created-from-a-fork) so the branch can be updated for a merge. Once you submit your PR, a Docs team member will review your proposal. We may ask questions or request for additional information. - We may ask for changes to be made before a PR can be merged, either using [suggested changes](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/incorporating-feedback-in-your-pull-request) or pull request comments. You can apply suggested changes directly through the UI. You can make any other changes in your fork, then commit them to your branch. - As you update your PR and apply changes, mark each conversation as [resolved](https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/commenting-on-a-pull-request#resolving-conversations). - If you run into any merge issues, checkout this [git tutorial](https://github.com/skills/resolve-merge-conflicts) to help you resolve merge conflicts and other issues. ### Your PR is merged! Congratulations :tada::tada: The team thanks you :sparkles:. Once your PR is merged, your contributions will be publicly visible on the [Anki xiehanzi](https://github.com/krmanik/Anki-xiehanzi).