We use github for our codebase. You can start by reading How To Pull Request.
We use git-flow as our branch organization, as known as FDD
We are using Github Issues for our public bugs. We keep a close eye on this and try to make it clear when we have an internal fix in progress. Before filing a new task, try to make sure your problem doesn’t already exist.
Providing a reduced test code is a recommended way for reporting issues. Then can placed in:
Please do not report the safe disclosure of bugs to public issues. Contact us by Support Email
Before you submit your Pull Request (PR) consider the following guidelines:
In your forked repository, make your changes in a new git branch:
git checkout -b my-fix-branch develop
Create your patch, including appropriate test cases.
Follow our Style Guides.
Commit your changes using a descriptive commit message that follows AngularJS Git Commit Message Conventions. Adherence to these conventions is necessary because release notes are automatically generated from these messages.
Push your branch to GitHub:
git push origin my-fix-branch
In GitHub, send a pull request to kitex:develop
Also see Pingcap General advice.
Good resources: